make force-tag gone

Dave Jones davej at redhat.com
Wed Sep 10 22:03:33 UTC 2008


On Tue, Sep 09, 2008 at 10:22:28PM +0000, Kevin Kofler wrote:

 > Because that's what the kernel uses and why they don't need force-tag. And even 
 > that doesn't completely eliminate the need for force-tag, because the mistake 
 > could be somewhere other than the specfile, e.g. a patch you forgot to cvs add.

FTR, I use force-tag a *lot*.

Here are some of the scenarios..

make tag ; make build
oh crap, ppc doesn't build.
disable option in config-ppc
cvs commit
make force-tag  (to retag the config-ppc file with the same version as everything else)

Now, I could bump the specfile and add "disable option foo on ppc" but if I did
this, our changelogs would be absolutely enormous, and for very little gain.

Another scenario..

- do a rebase
- cvs commit
- make tag ; make build
- crap, I forgot to add the .sign for the bz2
- cvs add patch..bz2.sign
- make force-tag (to tag the bz2.sign the same as the rest)

Again, adding an additional entry to the specfile because I forgot to add a file
is just going to bloat the changelog into something ridiculous.

There are other examples too where this has proven invaluable.

I've been away a week or so, so missed the rationale behind all this.
So why has this gone away ?

	Dave

-- 
http://www.codemonkey.org.uk




More information about the fedora-devel-list mailing list