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.
Right. And when NSS does an official release, have client.mk pull from that official tag until such time as a new NSS_CLIENT_TAG_YYYYMMDD interim snapshot gets created.
That way changes to the NSS pull become visible to the standard tools such as Bonsai and Tinderbox. If updating NSS causes a build to turn red, as I recall it has at least once in the past, it'll be easier for folks to figure out what happened.
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.
I don't see how that could be easier than changing the single line in client.mk.
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto
