Suggestion for cvs tag handling

[Nicolas Mailhot]

Le vendredi 07 mars 2008 à 18:36 +0000, Bill Crawford a écrit :
> On 07/03/2008, Till Maas <opensource at till.name> wrote:
> 
> >  Example:
> >
> >  1) edit foo.spec with version 1, release 1
> >  2) make commit tag build
> >  (immutable) tag is foo_1-1_fc9-build1
> >  and it does not build
> >  3) add missing patch
> >  4) make commit tag build
> >  (immutable) tag is foo_1-1_fc9-build2
> >  5) build succeeds
> >  6) cronjob creates immutable "alias tag" foo_1-1_fc9 with same contents as
> >  foo_1-1_fc9-build2
> >
> >  The naming scheme for the temporary tags with -buildX suffix can of course be
> >  arbitrary.
> 
> Yes, that's exactly what I was trying to say ...

As long as it works with the following workflow:
1. extract current package data from dainbramaged VCS (make srpm)
2. do some changes while blissfully ignoring the VCS existence
3. test them (mock, make scratch-build) and produce a new shiny new srpm
4. get it built and registered (cvs-import+cvs update+make build, would
be great to have a single atomic command)

Please make sure 4. stays simple if not simpler

-- 
Nicolas Mailhot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Ceci est une partie de message
	=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20080307/08bf0730/attachment-0002.bin