dealing with ports that can't upgrade

2008-06-21 Thread paul beard
So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want upgraded or that can't be upgraded? Something as simple as a .ignore file in the port directory or an entry in a list in ports.conf . . . In the case of metacity

Re: dealing with ports that can't upgrade

2008-06-21 Thread Ryan Schmidt
On Jun 21, 2008, at 3:19 PM, paul beard wrote: So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want upgraded or that can't be upgraded? Something as simple as a .ignore file in the port directory or an

Re: dealing with ports that can't upgrade

2008-06-21 Thread paul beard
On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Jun 21, 2008, at 3:19 PM, paul beard wrote: So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want upgraded or that can't be upgraded?

Re: dealing with ports that can't upgrade

2008-06-21 Thread Ryan Schmidt
On Jun 21, 2008, at 4:12 PM, paul beard wrote: On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt wrote: On Jun 21, 2008, at 3:19 PM, paul beard wrote: So I have this problem where I can't upgrade metacity until I get Leopard. Is there a way to have MacPorts simply ignore you don't want

Re: dealing with ports that can't upgrade

2008-06-21 Thread paul beard
On Sat, Jun 21, 2008 at 2:28 PM, Ryan Schmidt [EMAIL PROTECTED] wrote: On Jun 21, 2008, at 4:12 PM, paul beard wrote: On Sat, Jun 21, 2008 at 2:08 PM, Ryan Schmidt wrote: On Jun 21, 2008, at 3:19 PM, paul beard wrote: So I have this problem where I can't upgrade metacity until I get

Re: dealing with ports that can't upgrade

2008-06-21 Thread Rainer Müller
paul beard wrote: Do we really want people ignoring available upgrades? I don't think that's a good feature to add. If the upgrade doesn't install, why waste the cycles on it? And if a port's current version is the only one that works for a given use case, do we want to force an

Re: dealing with ports that can't upgrade

2008-06-21 Thread Rainer Müller
Rainer Müller wrote: I think you could just create a local repository with the old version of the port, overriding the version from the official tree. Another possibility: $ sudo port upgrade outdated and not metacity This prevents the upgrade of metacity while applying all other upgrades.