Error upgrading xrender on Panther

[Jeremy Huddleston]

Can you please see:

http://trac.macports.org/ticket/17429#comment:

I think if you pull in xorg-libX11 first, it'll be fine, but I need  
someone to test that first...


On Nov 30, 2008, at 07:49, Chris Janton wrote:

> On 2008-11-30 , at 07:13 , Chris Janton wrote:
>
>> Ticketed.
>
>
>> #17436: xrender fails to upgrade on Panther
>> ----------------------------------- 
>> +----------------------------------------
>> Reporter:  face@…                |       Owner:  macports-tickets@…
>>     Type:  defect                |      Status:  closed
>> Priority:  Normal                |   Milestone:  Port Bugs
>> Component:  ports                 |     Version:  1.6.0
>> Resolution:  wontfix               |    Keywords:
>>     Port:  xrender               |
>> ----------------------------------- 
>> +----------------------------------------
>> Changes (by toby@…):
>>
>> * status:  new => closed
>> * resolution:  => wontfix
>
> So how about maybe something like this?
>
> If a change to a port (for whatever reason) is known to break or not  
> work on panther
>
> Create a "new" port, maybe named something like "xrender-panther",  
> that is the state of the port prior to the latest upgrade.
>
> It would be incumbent on people using panther to uninstall the "old  
> but non-working" port and install the "new" port that keeps  
> everything "the way it was".
>
> The "new" port can be "nomaintainer". It wouldn't be changed any  
> more, so folks running Panther wouldn't have to worry about any  
> future upgrades.
>
> Just a thought.
>
> 8)
> ----------------------------------
> Chris Janton  - face at CentosPrime dot COM
> Netminder for Opus1.COM
>
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users