Re: [PATCH 0/3] cogito spec file updates

[Chris Wright <chrisw@osdl.org>]

* Petr Baudis (pasky@ucw.cz) wrote:
> Dear diary, on Tue, May 03, 2005 at 09:35:36PM CEST, I got a letter
> where Chris Wright <chrisw@osdl.org> told me that...
> > * Chris Wright (chrisw@osdl.org) wrote:
> > > Here's the outstanding updates for the spec file, up to 0.8-2 which is
> > > the latest on kernel.org.
> > > 
> > > 	http://www.kernel.org/pub/software/scm/cogito/RPMS/
> > 
> > What's your method for creating a release tarball?  If it were formalized
> > (i.e. Makefile rule), then it'd be simple to use VERSION to drive the
> > spec file, and it'd only need updating for real content changes (similar
> > to what Kay did).
> 
> For now, I do it so seldom that I just manually do
> 
> 	cg-log >Changelog
> 	cg-export ~/cogito-0.9
> 	cp Changelog ~/cogito-0.9
> 	cd ~
> 	tar cvvfz cogito-0.9.tar.gz cogito-0.9
> 
> OTOH, I'd like to change this all to just
> 
> 	cg-export ~/cogito-0.9.tar.gz
> 
> when I get to merge the relevant patches; I'm not sure there is so much
> of a value to bundle the Changelog; just get the git tree and do cg-log
> on your own, or use the web interface.
> 
> I might however have some private mkrelease.sh script which would do
> 
> 	echo "$1" >VERSION
> 	update-spec-file
> 	echo "$1" | cg-commit
> 	cg-tag "$1"
> 
> or something.

If you had a Makefile target like the one Mark Allen just posted, would
you use that?  I'd simply add a git.spec: rule, and have git.spec built
as a dependency for tarball.

> BTW, did you have a particular reason to split the .spec file updates to
> three parts? I think it doesn't make much sense and it'd be probably
> enough to update it at once, when we are not doing it at the right time
> anyway.

Just because that's how I had them locally, and it keeps the file
revision history intact (I don't mind how you prefer to pull them in).

thanks,
-chris