Requirements gathering for new package source control

[Horst H. von Brand]

Kevin Kofler <kevin.kofler at chello.at> wrote:
> Christoph Höger <choeger <at> cs.tu-berlin.de> writes:
> > It would be a great thing, if I could control all that from my own
> > versioned repository copy with some 'make <USUAL_STEP>' commands and
> > finally merge my changes back especially when testing builds for
> > multiple releases.

> Why don't you just commit the changes even if  you don't know yet whether
> they build?   Especially  for  a small   package where   you're  the sole
> maintainer, it won't really matter if CVS HEAD isn't always buildable.

If you want do be able to do something like "git bisect" (sorry for the SCM
mention) it is very useful if each (official, public) development point at
least builds OK.
-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                    Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria             +56 32 2654239
Casilla 110-V, Valparaiso, Chile 2340000       Fax:  +56 32 2797513