Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#22640 closed defect (invalid)

libungif: requires X by default?

Reported by: myrrhlin@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: Cc:
Port: libungif

Description

Updating my quite old macports I was surprised to find xorg-* packages being required by one of them, since I had not needed it before for any of my installed packages. [I have Apple's X11.app from the Developers Tools installed.] It was especially surprising since I was being selective about upgrades and checking dependencies as I went. Eventually I determined libungif to be the culprit.

I understand that substantial changes to ports may make use of new packages, and have no objection to this dependence, if it is indeed a new one.

Not being too familiar with the ports system innards, I don't know if this is a defect. Perhaps I am simply not understanding something. But from my standpoint, the following makes no sense (apologies for poor formatting):

$ port deps libungif

Full Name: libungif @4.1.4

libungif has no Build Dependencies, Runtime Dependencies, Fetch Dependencies, Library Dependencies, Extract Dependencies

$ port dependents xorg-libX11

libungif depends on xorg-libX11

I'm at a loss for what to do with this. I don't want two X11 systems installed.

Change History (2)

comment:1 Changed 15 years ago by jmroot (Joshua Root)

Resolution: invalid
Status: newclosed

Libungif does not depend on the X libs unless the x11 variant is selected. The port dependents output may be due to #13054, but that does not affect what will be installed when you upgrade.

comment:2 Changed 15 years ago by myrrhlin@…

and yet, i did not specify the variant +x11, and the xorg-* ports were installed when i upgraded libungif.

Note: See TracTickets for help on using tickets.