threads / patch / 475

patch, 3 partsRe: [PATCH 0/3] cogito spec file updates

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

## tl;dr

3 messages between May 4, 2005 and Sep 19, 2005. Diffs are folded; open one to read it.

replies: 2people: 2as markdown or json

Horst von Brand· May 4, 2005, 14:54 UTC · lore
"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
H. Peter Anvin· May 4, 2005, 15:01 UTC · re: Horst von Brand · lore
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
Horst von Brand· Sep 19, 2005, 21:58 UTC · lore

Re: Garbage in .git directories???

H. Peter Anvin <hpa@zytor.com> wrote:
[...]
> FWIW, using cg-clone (using git-core 0.99.6 and cogito 0.14.1) I keep
> finding a directory in .git which consists of a single DEL character
> (\177).

Using latest cogito (0.15 63ef5488c38b6660c72f042d4aa3015d72a3bd28) + latest git (0.99.7), cloning locally I don't see that. My older repositories (cloned over the net at various times or made locally) don't show it either.

-- 
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

← back to recent threads