On Fri, July 18, 2008 6:15 pm, James G. Sack (jim) wrote:
> [EMAIL PROTECTED] wrote:
>> I'm about to embark on a large project which basically consists of
>> maintaining a branch of the CentOS distribution. A consulting client
>> modifies a few rpm's, includes a few of their own, and ships this thing
>> on
>> appliances. We want to be able to keep track of exactly what went into
>> each machine and be able to reproduce if necessary.
>
> ..
>
>>..I don't so much like the fact that it
>> doesn't seem to implement something as simple as keywords (So I can't
>> put
>> $Version:$ in the /etc/motd and know what the version of this distro
>> is),
>
> I guess keyword ("keyword junk" as I have seen some people call it) may
> be mostly incompatible with distributed SCM since every repository would
> need to have different keyword values, and that would make one more
> exception to consider when merging.
>keyword expansion is just plain evil. Anything that mungs source is evil. > 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? OTOH, I see that Hg seems to have a > keyword feature waiting in the wings, so maybe it's not all "keyword > junk" in everyone's eyes. Hmmm, I suppose with distributed SCM there > must be (exactly?) one authoritative repo used for building > distributions, eh? > svn has "attributes" but IIRC they don't version and attach at a higher level than individual configuration items. > .. > > Regards, > ..jim > > > -- > [email protected] > http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list > -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
