[repo-coord] Re: Repo information inside rpm?

[Jeff Pitman]

On Monday 16 August 2004 23:01, Morten Kjeldgaard wrote:
> > 1. URL can be embedded in Vendor and/or Packager.
>
> No. The URL should point to the home-page of the program in the
> package.

Bzzzt. Not that URL.  For example:

URL:	http://python.org/
Vendor:	PyVault RPMS <http://python.org/pyvault>
Packager:	Jeff Pitman <http://symbiont.mn.sabren.com>

There are three URLs here.  Yes, they're static. But, I think it's 
useful to have.

> > 2. Dist should be munged using some well thought out dist tag
> > appended to the release.
> > 3. Ditto #2 for release.
>
> I don't grok what you mean here?? The point in my original proposal
> was that all the repos are different, but these differences could be
> handled with the same keyword scheme.

Just what Dag said earlier is what I meant:

|On Saturday 14 August 2004 01:03, Dag Wieers wrote:
|> 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.

> > 4. Arch is obtainable here: rpm -q --qf "%{arch}"
>
> No. We are not talking about the RPM architecture, but the Apt/Yum
> architecture, typically part of the path in the sources.list/yum.conf
> files.

Hmm. What you mention here and in the remains of the email has me 
thinking that maybe a change upstream in Apt and Yum is order, rather 
than tacking this onto RPM.  If you're just looking for where you got 
the package so you can write a script that can refetch/rebuild from the 
same location automatically, then there should be other ways to do 
this.  Is there a general direction you're taking this?  Maybe we can 
throw that around and see where it goes.

take care,
-- 
-jeff