Re: Suggestion for cvs tag handling

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le vendredi 07 mars 2008 à 18:36 +0000, Bill Crawford a écrit :
> On 07/03/2008, Till Maas <opensource@xxxxxxxxx> 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

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux