Re: [PATCH 0/3] cogito spec file updates
- From
Petr Baudis <pasky@ucw.cz>
- Date
- May 3, 2005, 21:44 UTC
- Message-ID
- <20050503214401.GE15995@pasky.ji.cz>
- In-Reply-To
- <20050503211527.42339.qmail@web41208.mail.yahoo.com>
Dear diary, on Tue, May 03, 2005 at 11:32:16PM CEST, I got a letter where Chris Wright <chrisw@osdl.org> told me that...
Show 12 quoted lines
> * Petr Baudis (pasky@ucw.cz) wrote: > > 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?
No, I definitively won't use that:
(i) The created tarball is Evil. It does not contain everything in a subdirectory.
(ii) I don't want to have yet another place which I'm supposed to keep up to date with regard to what should be packaged. That's one of the things the SCM is for, and it already records precisely this information, so I'd actually use it. cg-export foo.tar.gz is the perfect tool for this.
> I'd simply add a git.spec: rule, and have git.spec built > as a dependency for tarball.
I wouldn't accept this neither. If git.spec is already version controlled, it should be up-to-date in the version control. Therefore, you need to update it at the time of release, not at the time of generating the tarball.
-- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor