Date: Mon, 12 Apr 2004 23:39:46 -0700 From: Kris Kennaway <kris@obsecurity.org> 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: <20040413063946.GA26134@xor.obsecurity.org> In-Reply-To: <407B828F.1000600@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> <20040413054109.D730D43D1F@mx1.FreeBSD.org> <407B828F.1000600@pacific.net.sg>
next in thread | previous in thread | raw e-mail | index | archive | help
--wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 13, 2004 at 02:02:55PM +0800, Erich Dollansky wrote: > There will be the need for a central version manager. All versions are=20 > stored on different place. The central version manager tells new=20 > packages where the requested versions are stored. >=20 > A system like this would overcome all problems you could when moving=20 > from GNOME 2.4 to 2.6. You could keep and even work in 2.4 while 2.6 is= =20 > installed. You then have the chance to start each version direclty or=20 > you start the default version. >=20 > Of course, the central version manager must also know which version is=20 > the default version of each package the user wants to use. Please let us know when your implementation is ready. In the meantime, let's not hijack Garance's thread any further. Kris --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAe4syWry0BWjoQKURApSNAKD0RuqAmPz7Il3l2oQTAEMGqFQLMQCg+j1Z oIQf939YPArHfB4mak5vxro= =Pthu -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040413063946.GA26134>