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

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

From
Horst von Brand <vonbrand@inf.utfsm.cl>
Date
May 4, 2005, 14:54 UTC
Message-ID
<200505041454.j44Eslpg004032@laptop11.inf.utfsm.cl>
In-Reply-To
<hpa@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> said:
Show 5 quoted lines
> Petr Baudis wrote:
> > 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.
Show 5 quoted lines
> What I usually do is to have a *.spec.in file, and have my release 
> script generate the *.spec file.  I usually have a "version" file 
> checked into the SCM from which all version information derives, 
> including what to put in the *.spec file as well as what to name the 
> subdirectory.

Right. Note that this is /not/ autoconfiguring .spec from .spec.in, you are "just" automating the process I do by hand.

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513
Next: H. Peter Anvin
Message 1 of 3 in “Re: [PATCH 0/3] cogito spec file updates”
  1. Horst von BrandMay 4, 2005
  2. H. Peter AnvinMay 4, 2005
  3. Horst von BrandSep 19, 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.