Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)

[Kris Kennaway]

On Tue, Mar 20, 2007 at 03:47:25PM -0700, Doug Barton wrote:
> Alexander Leidinger wrote:
> >Quoting Rene Ladan <r.c.ladan at gmail.com> (Tue, 20 Mar 2007 21:20:18 +0100):
> >
> >>Doug Barton schreef:
> >
> >>>As for the requirements in the ideas page ...
> >>>
> >>[...]
> >>>    * storing old copies of shared libraries after shmajor number change
> >>>in /usr/local/lib/compat/pkg
> >>>
> >>>Portmaster doesn't do this currently. I have mixed feelings about
> >>>whether this is even a good idea or not. I'd be happy to elaborate on
> >>>why if anyone cares.
> >>>
> >>[...]
> >>
> >>Not having a /usr/local/lib/compat/pkg is cleaner IMO.
> >
> >It requires you to have all software up-to-date after a library version
> >bump. This is not always desired.
> 
> Can you explain in more detail when and why that might be the case? 
> What I'm trying to figure out is where the 80/20 line is here.

See e.g. the recent UPDATING entry for gettext and consider what would
happen if the user didn't jump through those hoops but only updated
gettext alone.

With portupgrade, the old library is preserved so all is fine.

Kris