Skip to content
This repository

Feature: add (optional) repodata generation for RPMS.all #2

Closed
zyv opened this Issue · 4 comments

2 participants

Yury V. Zaytsev Dag Wieers
Yury V. Zaytsev
Collaborator
zyv commented
<zaytsev> dag-, hmmm... # do not generate md for 'all', just the links is what I'm reading in the source code. why so?
<dag-> zaytsev: we used to, but generating the metadata took simply too long
<dag-> zaytsev: the RPMS.all was mostly done to find any package, without needing to go through all repositories
<dag-> I plan to change this too, the RPMS.repo was needed for apt-get, but that's quite moot nowadays
<dag-> so I plan to change the directory structure
<zaytsev> dag-, well, with 5-6 channels and local packages it's not so fun to put them all into yum.conf instead of just one entry
<dag-> and with createrepo --update, we could reinstated metadata in 'all'
<zaytsev> would be nice if this could would be an option, maybe disabled by default
<dag-> indeed
<zaytsev> shall I create and issue :-) ? now I really need to get back to my stuff
<dag-> in fact, I was contemplating allowing to virtually merge repositories
<dag-> also the default options to createrepo could be improved to allow for sqlite metadata as well
<dag-> you have my permission ;-)

Roger!

Yury V. Zaytsev
Collaborator
zyv commented

Depends on #13; also shall I file an issue for flexible merging / mixing or this is implied in #9 + #12? I mean one could allow to define repositories like this:

[rhel-6Server-i386]

os = ...
updates = ...

rolling = (os, updates)

and have mrepo to merge os + updates and generate metadata for rolling. This would be really cool to have, wouldn't it?

Dag Wieers
Owner

At some point merging repositories was possible by using mrepo:///channel links (and having more than one pointing to an existing repository:

rolling = mrepo:///os mrepo:///updates

Which would basically cause the rolling repository to have the packages from os and updates symlinked. Not sure if this still works today. I think this belongs in a separate feature request if we want to change how it works/fails today.

Dag Wieers
Owner

The RPMS.all repository will now automatically have repository metadata generated, so it works as a real repository. I decided not to make this optional since we now have --update with createrepo anyway so the impact should not be that big.

Yury V. Zaytsev
Collaborator

Hmmm, if this works:

At some point merging repositories was possible by using mrepo:///channel links (and having more than one pointing to an existing repository:

then this issue can be closed indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.