On Thursday 14 May 2009 15:36:29 Duncan Mac-Vicar Prett wrote:
Elmar Stellnberger wrote:
What about simply utilizing a previously unused rpm-tag to directly determine via the rpm-header where a package came from? Then we do not need to parse the whole history just for this purpose! I have had a look at all header entries and have found a promising up to now unused candidate: RPMTAG_SOURCE
For the future RPMTAG_SOURCE could carry the Buildservice-URL a package is provided via. SOURCE = http://download.opensuse.org/repositories/KDE:/Community/openSUSE_11.1
well, you know this is already present ? # rpm -qp --qf "%{DISTURL}\n" kde3-mailody/kde3-mailody-0.5.0-1.1.x86_64.rpm obs://build.opensuse.org/KDE:Community/openSUSE_11.1/8509726c16b137b6f090460af5067d4c-kde3-mailody $OBS_INSTANCE/$PROJECT/$REPOSITORY/$SRCREV-$PACKAGE
RPMTAG_DISTRIBUTION could then no longer be complicated with the info already present in RPMTAG_ARCH, but extended with a hint like Buildservice/Core:
How do you handle mirrors in this case?
-- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux Fatou 2.6.29-6-default #1 SMP 2009-03-24 15:38:18 +0100 x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org