But there is a real use to having it in the filename and EVR info,
despite the fact that we're using the release tag for something it
wasn't designed for.
There is no use for repo tags in EVR info.
brainstorming:
- foo-repository:
$ rpm -q --qf "%{name} %{repository}\n" foo
foo rh.fc3.base.games
- repository-url:
$ rpm -q --qf "%{repositoryurl}\n" rh.fc3.base
[base]
name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever
enabled=1
gpgcheck=1
- settings via rpm
# rpm --set repositoryurl=rh.fc3.base=enabled=0
- repository-update:
# yum update --repository rh.fc3.base.games
could it be possible to add a repo-tag in this way
vendor? . release? . repo? . class = system-config-packages?
eg. "redhat . fedora core 3 . base"
rh.fc3.base.server
rh.fc3.base.system
rh.fc3.base.games
eg. "redhat . fedora extras 3 . updates"
rh.fe3.updates.server
rh.fe3.updates.system
rh.fe3.updates.games
eg. "redhat . fedora extras 3 . testing"
rh.fe3.testing.server
rh.fe3.testing.system
rh.fe3.testing.games
eg. "fedora us . fedora extras 3"
fdrus.fe3.server
fdrus.fe3.system
fdrus.fe3.games
eg. "freshrpms.net . fedora extras 3"
frn.fe3.server
frn.fe3.system
frn.fe3.games
eg. "dag.wieers . fedora extras 3"
dagw.fe3.server
dagw.fe3.system
dagw.fe3.games
--
shrek-m