The 1.5.2 release happened soon after to the 1.5.1 release, and we
decided that there was no point in having a separate freeze for
1.5.2 - the 1.5.1 tag should be used, which is a good one. I realise
that it is about 6 months old now, which is a long time in the
world of third party software, but that's what happened. It was
also not practical to freeze pkgsrc at the time, being in the middle
of major buildlink work, amongst others.

Stoned told me that he used pkg_chk to upgrade a number of packages
(200 I think he said) You could also look at the *_SPECIFIC_PKGS
definitions, and at the bulk build mechanisms.

Regards,
Alistair


On Thu, Nov 01, 2001 at 11:36:44AM -0500, Christopher W. Richardson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> There doesn't seem to be a netbsd-1-5-PATCH002 tag on the files
> in pkgsrc. Was this an oversight, or is it not ready yet, or are
> packages no longer being tracked concurrently with src? (Or
> perhaps it's some other choice that I've missed). Also, in
> general, what is the best way to handle upgrading pkgs on
> machines that aren't running current? When you upgrade from, say,
> 1.5 to 1.5.1, do you (you being anyone who wants to comment)
> upgrade all of your packages, or just on an as needed basis?
> Also, is there a better (easier) way to do this than to write a
> script to parse output from pkg_info and feed it to make update?
> 
> TIA,
> Chris
> 
> Key fingerprint: 04B9 0F4F A999 D22F BFB7  6977 3FAE 5104 E387 4F31
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (NetBSD)
> Comment: Processed by Mailcrypt 3.5.6 and Gnu Privacy Guard <http://www.gnupg.org/>
> 
> iEYEARECAAYFAjvhehgACgkQP65RBOOHTzHvcwCgqye18JnJvQf1c1yBBBQYN5Ml
> OqoAoOT59iLoNXsy8BWcipAhlSNFAcNo
> =5EgP
> -----END PGP SIGNATURE-----