git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
CWChris Wright <chrisw@osdl.org>
Date
May 3, 2005, 21:32 UTC
Message-ID
<20050503213216.GF5324@shell0.pdx.osdl.net>
In-Reply-To
<20050503212142.GB15995@pasky.ji.cz>
* Petr Baudis (pasky@ucw.cz) wrote:
Show 37 quoted lines
> 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

Previous: Petr Baudis
Message 7 of 7 in “cogito spec file updates”
  1. 0/3 cogito spec file updatesChris Wright, May 3, 2005
  2. 1/3 cogito spec file 0.7-1Chris Wright, May 3, 2005
  3. 2/3 cogito spec file 0.8-1Chris Wright, May 3, 2005
  4. 3/3 cogito spec file 0.8-2Chris Wright, May 3, 2005
  5. Chris WrightMay 3, 2005
  6. Petr BaudisMay 3, 2005
  7. Chris WrightMay 3, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.