Carl Lowenstein wrote: > On Fri, Jul 18, 2008 at 7:11 PM, James G. Sack (jim) <[EMAIL PROTECTED]> > wrote: >> 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. >> > > If I may allude to an old discussion, isn't this an argument for > embedding people-readable tags in object files?
I only kinda-vaguely recall that discussion. What was the context and conclusion -- do you remember? In any case, I can think of something else to observe: embedded labels can not really be used to verify files -- you need a real hash authentication mechanism to do that, eh? But that wasn't the question here, I don't think ..so.. nevermind. :-) Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
