From owner-freebsd-ports Thu Feb 8 9:22: 3 2001 Delivered-To: freebsd-ports@freebsd.org Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by hub.freebsd.org (Postfix) with ESMTP id 80E5037B491; Thu, 8 Feb 2001 09:21:44 -0800 (PST) Received: from bmah-freebsd-0.cisco.com (bmah-freebsd-0.cisco.com [171.70.84.42]) by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id JAA16600; Thu, 8 Feb 2001 09:21:57 -0800 (PST) Received: (from bmah@localhost) by bmah-freebsd-0.cisco.com (8.11.1/8.11.1) id f18HLiN44975; Thu, 8 Feb 2001 09:21:44 -0800 (PST) (envelope-from bmah) Message-Id: <200102081721.f18HLiN44975@bmah-freebsd-0.cisco.com> X-Mailer: exmh version 2.3.1 01/19/2001 with nmh-1.0.4 To: W Gerald Hicks Cc: bmah@FreeBSD.ORG, ports@FreeBSD.ORG, Kal Torak Subject: Re: Ports updating... Good ways? In-Reply-To: <3A82547E.18AD4D26@cisco.com> References: <3A8208E7.C6EE4C24@quake.com.au> <20010208061814.5E6C5E6A17@netcom1.netcom.com> <200102080638.f186c9s39260@bmah-freebsd-0.cisco.com> <3A82547E.18AD4D26@cisco.com> Comments: In-reply-to W Gerald Hicks message dated "Thu, 08 Feb 2001 00:10:38 -0800." From: bmah@FreeBSD.ORG (Bruce A. Mah) Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_417760173P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 08 Feb 2001 09:21:44 -0800 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --==_Exmh_417760173P Content-Type: text/plain; charset=us-ascii If memory serves me right, W Gerald Hicks wrote: > (Hi Bruce :-) Hi Jerry! :-) > In thinking about this further, it seems to me there is also some > missing metadata that one would need to automate port upgrades reliably. > > There doesn't seem to be anything that relates previous versions of a > port to an updated one. At least not in a rigorous manner that could be > trusted by naive scripts... Recently-installed ports (recently-built packages maybe) contain meta-data that says where their port skeleton directory lives within the ports tree. pkg_info and pkg_version both use this data. For example: bmah-freebsd-0:bmah% grep ORIGIN /var/db/pkg/gnupg-1.0.4_3/+CONTENTS @comment ORIGIN:security/gnupg bmah-freebsd-0:bmah% pkg_info -q -o gnupg-1.0.4_3 security/gnupg bmah-freebsd-0:bmah% pkg_version -v | grep gnupg gnupg-1.0.4_3 = up-to-date with port I am not sure if any of the (three?) proposed ports/package upgrading tools use this field or not. Bruce. --==_Exmh_417760173P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6gtWn2MoxcVugUsMRAuKbAJ0fui1kqfUVhzl1tep4e0egovnORwCfc+/H l+qftPWq10uyncW4JHJZwKk= =GnzA -----END PGP SIGNATURE----- --==_Exmh_417760173P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message