On Tue, Jul 01, 2008 at 03:58:33PM -0700, Valerie Bubb Fenwick wrote: > On Fri, 27 Jun 2008, Will Fiveash wrote: > >> On Fri, Jun 27, 2008 at 09:46:11AM -0400, James Carlson wrote: >>> Will Fiveash writes: >>>> >> The problem I face is that krb-diag outputs its version which is useful >> when looking at its diagnostic output. As it is now in the kerberos >> repository the unexpanded SCCS keywords will be output which is useless. >> In addition, the idea is that the version of the script in the krb >> repository will be the canonical version and people should be able to >> download that version and run it (with the version info embedded in the >> script). Will this require a Makefile to produce a version of the >> script with its version info expanded? > > ON recently has added a new rule that no SCCS keywords can be used > as version strings going forward. There have been a few suggestions > from some SCM migration folks on alternatives, but most won't really > be exactly the same as what we have now & won't work until we move > to hg. > > ( http://opensolaris.org/os/community/on/crt/rti-nits/ ) > > for example, using a macro in a makefile that uses "hg tip" that > can be used for version information.
>>> I didn't find that in the transition document, and I'm not sure why. >>> The folks writing those documents have used hg for a while, and >>> perhaps it just seemed too "obvious" -- though it's not for someone >>> with a Teamware background. It probably should be there. >> >> I agree. This is one of the first things I needed help with. > > There was a KTD given by Mike Kupfer & Stephen Lau in 2007 on this, that > covered this as well. It's available internally on > http://ktd.eng/ , but as far as I know the slides are not also > available externally. (perhaps someone cc'ed here from the SCM team > could do so?) Again, yes, let's get the relevant SCCS/hg keyword info on the opensolaris pages which is where I looked and expected to find the latest info (not ktd.eng). And the standard for dealing with the issue that I'm dealing with (getting the current version # in a script) should be part of this. -- Will Fiveash
