[...] The problems with how Mozilla pulls NSS are: 1. NSS_CLIENT_TAG cannot be pulled by date. So it is difficult to reconstruct a past Mozilla trunk build. [...] The NSS team would like Mozilla (trunk builds, stable branches, or milestone releases) to always pull NSS by some static (non-floating) cvs tag [...]
Right.
But with "tag only" release like 1.7a, the problem extends from nightly trunk builds to more significant builds.
I think the solution hinted by John is indeed the bast.
The NSS team should stop providing a NSS_CLIENT_TAG tag, replace it by a NSS_CLIENT_TAG_YYYYMMDD tag that is static, and client.mk should point to some NSS_CLIENT_TAG_YYYYMMDD, with an update as regular as the current NSS_CLIENT_TAG update.
Maybe for convenience client.mk should get the name of the tag to use from an NSS file, so that the NSS team can update the reference tag easily.
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto
