On Thu, Jul 03, 2008 at 12:10:03PM +0100, Darren Moffat wrote: > James C. McPherson wrote: > > Shawn M Emery wrote: > >> In the near future it would be nice to have some form of keyword > >> expansion whether in one form or another. If everyone is in agreement > >> then we may want to consider the keyword extension for mercurial which > >> allows fairly easy interface to expand and contract keywords: > > > > One of the benefits of moving to Mercurial is that we can > > remove (or at least, massively decrease) our reliance on > > SCCS keywords that very, very frequently have absolutely > > no relationship to reality. > > > I think you'll find that the people on this mailing list > > are not in favour of what you suggest. > > I am very much in agreement with James. The issue has been brought up > and discussed in great detail - including a lot of internal to Sun > discussion with the services organisation. > > There are much better and more reliable tools for determining which > revision of a particular binary you have than source keywords. They > include (either on their own or in combination) but are not limited to: > pkgchk, pkg(5) [IPS], digest, md5sum, bart, showrev, elfsign, the online > fingerprint database.
Note however that I started this discussion because we have a self contained shell script (krb-diag) that we're making available via the www.opensolaris.org/os/project/kerberos page and I've placed it in an associated hg repository. Ideally we'd like to have the current version of the script expanded in the script in the hg repository and to have this version updated when someone does a hg push to update this repository. That way one does not have to run make to process the script just to get the version expanded. Or if it is deemed necessary to do makefile processing on the script perhaps the hg push could run make to process the updated script and install it in some build directory. This could be useful if there were a way to have a downloads section on the krb page that would retrieve the latest version from this build dir or directly from the hg repository if the version was in the script source. (As an aside, I've noticed that the opensolaris source browser Download link doesn't do that exactly when the examined file is a shell script like wx.sh. It just causes the raw script text to be displayed in the browser window which isn't quite the same as downloading.) As to the motivation for this, there are a number of copies of krb-diag out there in the wild of differing vintages so being able to see the version of krb-diag that produced the diagnostic output is useful. And given that we do not intend on trying to bundle this utility with Solaris at this point, the suggestion regarding pkg related utils is moot. -- Will Fiveash Sun Microsystems Office x64079/512-401-1079 Austin, TX, 78727 (TZ=CST6CDT), USA Internal Solaris Kerberos/GSS/SASL website: http://kerberos.sfbay Info about krb-diag: http://kerberos.sfbay/krb-tool-info.html http://opensolaris.org/os/project/kerberos/
