-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 12 Jun 2003, Soren Jacobsen wrote:

>On 06/12 22:24, Jim Wise wrote:
>> As far as I can tell, with regpkg as currently committed, if I compile
>> _identical_ code on two different dates, I get different version
>> numbers.  Plus which, is a pkg versioned 20030614 built from the branch
>> `newer' or older than one with the same version number built from
>> - -current?
>>
>> More damningly, if i compile newer code and then compile older code, the
>> older code gets a newer version number.  This, obviously, makes it
>> infeasible to include `affected' syspkg versions in SAs.
>
>Maybe the ident strings could be used? Find the most recent and use that
>as the date? Using the kernel revision seems just wrong, because it
>really has nothing to do with most utilities.

Using the version in osrelease.sh has the advantage of picking up the
current release number on release branches.  I agree that it is less
sensible in -current, but date, which implies an ordering between
branches which does not, in fact, exist, is much worse than this.

>Or perhaps I'm way off base. I'm not faimliar with syspkg yet.

Not really -- there is not currently a concept of an `OS Version'
distinct from the kernel version right now, though, which is why
snapshots up for download on ftp.netbsd.org have often used the version
from the kernel for this purpose as well...

- -- 
				Jim Wise
				jwise@draga.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (NetBSD)

iD8DBQE+6Tt0lGcH240chEIRAnrYAKCVLgkyJO6HQpMojZxxLqx8ynFFGQCgtW7X
VIyV93jdGE7+IcxxR8rz66Y=
=Q0eG
-----END PGP SIGNATURE-----