rpm -q --qf "%{DISTURL}\n" kdebase3 kdebase3-session kde4-kmahjongg kdeaddons3-kate python-kde3 kdepim3 srcrep:ea2b965c6714375c5b04984b9dc1f7f4-kdebase3 srcrep:ea2b965c6714375c5b04984b9dc1f7f4-kdebase3 srcrep:3a7c5e0e03ccc7bf009771b44c427695-kdegames4 srcrep:4820cd868700d8d3fdc67177fd85528c-kdeaddons3 srcrep:6884e1a3f7a8dd2a194823ce62df73eb-python-kde3 obs://build.suse.de/SUSE:openSUSE:11.1:Update:Test/standard/1b7482b2cf00d011a39eff2d5a03c3b1-kdepim3
It seems to return some kind of classification scheme intermangeled with a hash key for most cases. What I have proposed is to supply the primary repository URL the package can be redownloaded from in order to group packages by their zypp-installation source. However obs://build.suse.de/SUSE is no valid URL where I could redownload the package from. Ruediger Oertel schrieb:
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?
-- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help@opensuse.org