On Wed, 2008-03-05 at 13:23 -0500, Jesse Keating wrote: > On Wed, 2008-03-05 at 13:20 -0500, Colin Walters wrote: > > On Wed, 2008-03-05 at 13:17 -0500, Jesse Keating wrote: > > > On Wed, 2008-03-05 at 13:03 -0500, Colin Walters wrote: > > > > What remains to be implemented is the Koji side of things. The idea is > > > > that "make build" will run 'cvs commit; make tag koji', and that Koji > > > > will have a database of package Release tags, and increment them itself > > > > for each new build. It will generate the %changelog section from the > > > > CVS changelog between the last tag and the new one. > > > > > > We really don't want koji writing back to the CVS server. There is a > > > lot of benefit to koji having only readonly access to the source > > > control. > > > > This system wouldn't require koji writing to the CVS server. > > Sorry, I misread that. Still, why would you pull from koji instead of > the cvs server itself? The overall idea is that the release number is determined by the "build server", where "build server" can be either localhost (for make local), or Koji (for Fedora). So for local builds, you don't hit Koji to determine a release - we just create one, and then increment it from there. We don't want to distribute locally-built RPMs as if they came from Fedora, so giving them a .local disttag with a locally-determined release is a good thing, I think. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
