[repo-coord] Repo information inside rpm?

[Dag Wieers]

On Fri, 13 Aug 2004, Morten Kjeldgaard wrote:

> (1) put this in your .rpmmacros file (one line):
> 
> %distribution *url=%{repo} dist=%{dist} rel=%{rel} lang=%{?lang} arch=%{arch}
> comp=%{comp}*
> 
> (2) in the beginning of each .spec file, put something like the following:
> 
> #----------------------------------
> %define repo http://blablabla
> %define dist fedora
> %define rel 1
> %define arch i386
> %define comp testing
> #----------------------------------

Ok, I have some more remarks.

 + Why would you put the language in there ?

 + Why would you put the architecture in there ? It's already part of the 
   package.

 + What is the comp supposed to mean, and if it means component or a 
   seperate repository, it would mean you can't move it later without 
   rebuilding ?

Also, we are already using %dist for the visible disttag being rh8, fc2 
or el3. The real release however adds a number to the release like: 0.rh8, 
1.el3 and 1.fc2.

 
> Note: the values must reflect the unix path in the repo! (OBS! %dist has
> nothing to do with the %disttag sometimes discussed on the list!!)
> 
> > From this example, we would get a string in the Distribution tag:
> 
>    *url=http://blablabla dist=fedora rel=1 lang= arch=i386 comp=testing*
> 
> Using the attached python snippet, this will parse into:
> 
>    rpm http://blablabla fedora/1//i386 testing
> 
> which works as a sources.list file. Hehehe ;-)

Well, I think some of the values would be useful to have, but I don't 
think you're doing it for the right reasons. If the goal is to extract an 
Apt/Yum location, I don't think that is a good idea. What about i568 
packages that are part of the i386 repository or even x86_64 ? What about 
noarch packages ?

Why do you want to extract an Apt location ?

--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]