packages/ tools (Re: CVS down - git migration)

[Kacper Kornet]

On Wed, Jul 11, 2012 at 04:21:46PM +0200, Kacper Kornet wrote:
> On Wed, Jul 11, 2012 at 05:08:40PM +0300, Elan Ruusamäe wrote:
> > On 11.07.2012 16:03, Kacper Kornet wrote:
> > >A small doubt about it. Package rpm-build-tools is cloned to
> > >chroots used by builders. Are all this tools really needed there?
> > in src-builders probably (two setups both on ep09), but in
> > bin-builder, only builder script is needed, which i have symlink to
> > system package (so it can be kept up to date with normal package
> > upgrades).

> In src builders I prefer to keep it in clone of git repo. This way if I
> want to make a final check if the new changes don't break anything I
> don't need to produce rpm, upgrade it and in case of breakage downgrade.

> One more idea. The history of this additional files right now has to be
> set to new set of seperate branches. If someone wants them together with
> builder and adapther it needs to merge master and one of this new
> branches. But maybe this merge shouldn't be made on master. 

> This way we keep master clean for sbuilders, and what's more for
> building rpm packages rpm-build-toos.rpm. And if somebody wants to use
> the tools can use a separate branch Tools (or whatever it is called) in
> his rpm/rpm-build-tools local clone.

One comment: obvious drawback is that if someone modifies builder or
adapter this should be done on master and then merged to Tools. Changes
to other files should go to Tools directly. So probably too error prone.

-- 
  Kacper