begin quoting James G. Sack (jim) as of Fri, Jul 18, 2008 at 07:11:00PM -0700: > SJS wrote: > // > >> Seems like there ought to be some substitute for your purpose though -- > >> cannot a "build" operation create a build product containing a build id > >> reflecting (perhaps among other things) the repository "changeset" -- if > >> that is that the right term here? > > > > Is the the overall changeset that's important, or the release? > > Reading TR's mind :-) I was thinking that the need was to look at a > system at-hand and answer where the $#@ did this "version" originate, > and how can I reproduce it. Then (like your post referring to a > versioned release file), I did an aha-to myself saying that there is > probably an "official" build repository which creates the official > builds released into the wild.
Yup. If you automate that process (which you should do as much as possible), you can record date, time, username, machine, etc. in addition to the release number, just in case something funky went on. "Odd, every release with problems was done by 'Joe'. Maybe he's not following the proper procedure?" -- If it's tedious and you know it, delegate it! Stewart Stremler -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
