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

From: H. Peter Anvin <hpa@zytor.com>
Date: May 4, 2005, 15:01 UTC
Message-ID: <4278E3E2.3010001@zytor.com>
In-Reply-To: <200505041454.j44Eslpg004032@laptop11.inf.utfsm.cl>

Horst von Brand wrote:

Show 18 quoted lines

> "H. Peter Anvin" <hpa@zytor.com> said:
> 
>>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.
> 
> 
>>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.

Right, the .spec.in here doesn't imply the use of autoconf.

(That being said, if you *are* using autoconf, the "make release" target is also a good place to produce the autoconf generated files, being just another class of autogenerated-but-should-be-in-the-tarball files.)

	-hpa