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

On Wed, 14 Feb 2001 itojun@iijlab.net wrote:

>
>>Since package tiny versions will be monotonically increasing on the
>>release branch, if the last security patch for NetBSD-1.7 upgraded the
>>base-secsh-bin package to version 1.7.4, when the 1.7.1 release is
>>shipped, it will come with version 1.7.1.4 (or 1.7.1.5 if other changes
>>have come in in the meantime) of this package.
>
>	isn't it easier to have four digits, like "1.7.0.0" for NetBSD-1.7?

I'm not sure which is better, so yeah, I can have it work this way if
people want.  The current method (`uname -r`.${TINY_VERSION}) is easier
to generate, and more consistent with our release naming (it's not
NetBSD-1.5.0, after all), but yes, may be less clear.

What do people think?

One advantage of doing what you suggest, OTOH, is that it makes the
distinction between versions on the branch (1.7.0.0) and on the trunk
(1.7A.0) more clear...

- -- 
				Jim Wise
				jwise@draga.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE6ifWf2JhG4/qi8rQRAoTlAKCB2uIDMHqpCv6UY2kz+3IzbgAd/gCghYsO
zoJjAl309vJcq68nGdyzQzU=
=3bv1
-----END PGP SIGNATURE-----