Wiki-Update (Was: Re: How to update the package?)

[Thorsten Leemhuis]

Am Donnerstag, den 26.01.2006, 13:25 +0100 schrieb Nicolas Mailhot:
> Le Jeu 26 janvier 2006 12:35, Thorsten Leemhuis a écrit :
> > Am Donnerstag, den 26.01.2006, 11:57 +0100 schrieb Michael Schwendt:
> >>[...]
> >> Also make sure you prefer "make new-sources FILES=..." instead
> >> of "make sources FILES=...". The former will replace the "sources"
> >> file within CVS and not just add entries to it.
> >> "make tag" is missing in your steps, btw.
> >> [....]
> > We really should update the wiki with a proper, more detailed
> > description how to update a package.
> > The section "How do I update an existing package in CVS?" on
> 
> My stupid way of doing things is to just create a separate srpm for all
> branches (%{dist} is my friend), cvs-import them (whith the import script
> magically noticing already-uploaded sources and tagging everything as
> needed) then make plague.

There is one reason why I'm currently considering to forbid the use of
cvs-import for already imported packages: Most people won't run a diff
against the old package/the old spec this way before committing (or does
the script force a diff before committing? I never used it for anything
else than importing).

I run a "cvs diff -u" every time before I commit something and now and
then (every fifth package round about) I find debug leftovers or small
errors this way *before* committing them. Maybe I'm just to stupid and
other people never make such errors -- but I suspect they do.

CU
thl