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

[Kacper Kornet]

On Wed, Jul 11, 2012 at 05:34:59PM +0300, Elan Ruusamäe wrote:
> On 11.07.2012 17:26, Kacper Kornet wrote:
> >>>  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.
> rather create separate branch for builders if you want the checkout
> to be clean? you can even omit other files for builder (adapter*,
> *.spec, pldnotify*)

> as the tools are needed daily together with already existing tools
> like builder and adapter, sometimes new tools added too...

That's my plan B ;-). But seriously probably a better idea. As it will
force to be careful only the person maintaining sbuilder branch, not all
developers.

-- 
  Kacper