From owner-freebsd-ports@FreeBSD.ORG Mon Apr 12 22:49:47 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 34AAC16A4CE for ; Mon, 12 Apr 2004 22:49:47 -0700 (PDT) Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2276F43D1D for ; Mon, 12 Apr 2004 22:49:47 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (d317e6c8cf96ea866ab6c384ba00776d@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw6.prodigy.net (8.12.10/8.12.10) with ESMTP id i3D5majG006321; Mon, 12 Apr 2004 22:48:36 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 52C7752322; Mon, 12 Apr 2004 22:49:45 -0700 (PDT) Date: Mon, 12 Apr 2004 22:49:45 -0700 From: Kris Kennaway To: Erich Dollansky Message-ID: <20040413054945.GA25540@xor.obsecurity.org> References: <407B6B43.2050507@pacific.net.sg> <20040413042929.GA24603@xor.obsecurity.org> <407B780F.5030102@pacific.net.sg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline In-Reply-To: <407B780F.5030102@pacific.net.sg> User-Agent: Mutt/1.4.2.1i cc: Garance A Drosihn cc: freebsd-ports@freebsd.org cc: Kris Kennaway Subject: Re: Second "RFC" on pkg-data idea for ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Apr 2004 05:49:47 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 13, 2004 at 01:18:07PM +0800, Erich Dollansky wrote: > Hi, >=20 > 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= =20 > >>be able to automatically overcome this problem with installing the=20 > >>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=20 > not allow to keep the old version in parallel allowing one application=20 > using the old one while the other application uses the new one. > > > >>This could lead to a general system where any number of different=20 > >>versions of a package or port could be installed on the machine without= =20 > >>any interferance. > > > > > >That's a very different problem. > > > But it is what I ment. >=20 > Erich That's off-topic for the present discussion then, because Garance wasn't asking for blue-sky wishlists of features for the ports tree, he was asking for comments on his specific proposal. Kris --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAe394Wry0BWjoQKURAhRxAJ9YDoAog90wovN/hlDq/efUo3EbNgCfd8qV Jw5U7w1C8zncuO5fuh7L7LM= =OJ5e -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD--