Date: Mon, 12 Apr 2004 23:41:03 -0600 From: Robin Schoonover <end@endif.cjb.net> To: Erich Dollansky <oceanare@pacific.net.sg> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: Second "RFC" on pkg-data idea for ports Message-ID: <20040413054109.D730D43D1F@mx1.FreeBSD.org> In-Reply-To: <407B780F.5030102@pacific.net.sg> References: <p0602040cbca10a7dbe52@[128.113.24.47]> <p0602040dbca11349ce03@[128.113.24.47]> <407B6B43.2050507@pacific.net.sg> <20040413042929.GA24603@xor.obsecurity.org> <407B780F.5030102@pacific.net.sg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Apr 2004 13:18:07 +0800, Erich Dollansky wrote: > Hi, > > Kris Kennaway wrote: > > On Tue, Apr 13, 2004 at 12:23:31PM +0800, Erich Dollansky wrote: > > > >>It would be real helpfull to users if the package or port system would > >>be able to automatically overcome this problem with installing the > >>needed version in a way that the installed versions stays intact. > > > > > > Take a look at the portupgrade port, I think that's what you're trying > > to describe. > > > If I understood portupgrade right, it upgrade a port but it still does > not allow to keep the old version in parallel allowing one application > using the old one while the other application uses the new one. That's rather difficult to do. The biggest problem you hit right away is a port will (usually) conflict with itself. In other words, all the versions will want the same files in the same place. So in order to fix this properly, you'd have to have separate places for each file (or different file name). Then you need some way for application x and application y which each depend on your port of multiple versions to use the port version you want them to. -- Robin Schoonover (aka End) # # We have them just where they want us. -- James Kirk #
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040413054109.D730D43D1F>