Ports management tools in the base (Was: Re: cvs commit:
pav at FreeBSD.org
Wed Mar 21 10:44:28 UTC 2007
Andrew Pantyukhin píše v st 21. 03. 2007 v 11:31 +0300:
> On 3/21/07, Alexander Leidinger <Alexander at leidinger.net> wrote:
> > When you need a program which needs a newer lib than installed on a
> > production system, but you don't get a maintenance window to update
> > all other programs which use this lib, then not having the old lib
> > will hurt.
> > When the reason for the library version bump also requires to change
> > some parts in the source of the programs which make use of the lib,
> > you have to update all programs at once. If some programs have bugs in
> > more recent versions which you can't accept in production and when you
> > need to install a program which needs the new lib version, you are
> > busted when you don't have the old lib around.
> But don't you smell an architectural flaw here (of the
> ports system) and don't you feel that working around it
> in a tool in the base system might only mess things up
> even more?..
No I don't see a systematic flaw here. Or you suggest we reset all
shmajors everywhere to zero?
Pav Lucistnik <pav at oook.cz>
<pav at FreeBSD.org>
The hottest spot in the solar system is neither Mercury, Venus,
nor St. Louis in the summer.
-- WUSTL Press Release
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?=
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20070321/f0c39228/attachment.pgp
More information about the freebsd-ports