Date: Thu, 08 Feb 2001 09:21:44 -0800 From: bmah@FreeBSD.ORG (Bruce A. Mah) To: W Gerald Hicks <gehicks@cisco.com> Cc: bmah@FreeBSD.ORG, ports@FreeBSD.ORG, Kal Torak <kaltorak@iname.com> Subject: Re: Ports updating... Good ways? Message-ID: <200102081721.f18HLiN44975@bmah-freebsd-0.cisco.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102081721.f18HLiN44975>