On Thu, 2008-09-11 at 14:47 -0700, Toshio Kuratomi wrote: > Jesse Keating wrote: > > Really it comes down to a premature desire to clean up the way that Koji > > builds things. For lack of something easier, koji builds from a CVS tag > > based on the N-V-R of a package build. For lack of knowledge of > > something easier, the thought is that tag is the only thing we can use > > to get back to the actual source used for a build. It's not. I've been > > told of at least one way to use something different, the CVS/Entries > > file. Yeah, it might take a little work to cook up an app to go from > > that to the source, but that's fine, that's work the person who wants > > this has to do. > > > This specific implementation would be a bad thing. Instead of having a > nice, SCM abstract method of communicating to koji what to build from > (the tag) you'd be resorting to CVS specific knowledge. Okay, so scm.checkout grows another outparam that return the reproducability information. You'd get a tag from git, Entries from CVS, revision number from SVN... This isn't materially more work. - ajax
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
