Error upgrading xrender on Panther

[Ryan Schmidt]

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

> 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.

That's probably not going to happen at all, mainly for the reason  
that it is not known that things are going to break or not work on  
Panther because most people don't test on Panther anymore. As bug  
reports get filed, then individual decisions can be made on how to  
resolve each issue. My hope is that one could fix the ports to work  
on Panther, rather than having to divide the universe by creating  
copies of older versions of the ports, which is very messy.