Guess I'll pick that up. We're still using genbasedir & friends for an apt-rpm repository which only works via a legacy /opt rpm version that we keep for exactly this reason.
OTOH switching to a format which is mainly driven by a community that does not seem keen to collaborate is not very pleasing either.
Has anyone any links/ information about the reasons as to why repo-md has the format that it has today? Is there any interest to review this format and potentially come up with a new blueprint? While I am personally very interested in sorting this I can only see this work with input and support from multiple drivers which would then collaborate on this new format and actually use it. I don't just want to do it my way, but have an accepted, comfortable solution that is well engineered and has a good future with rpm5.
Any thoughts? Is there an option/ solution I am missing?
On 24/02/2011, at 7:38, Jeff Johnson <firstname.lastname@example.org> wrote:
> On Feb 23, 2011, at 1:30 PM, Matthew Dawkins wrote:
>> We tried using rpmrepo, but it doesn't support some time saving features like createrepo --update the last time I we checked. Yum is only needed by createrepo, otherwise we use smart for our package manager.
> Quoting myself:
> The output of rpmrepo was identical to what was in use by yum when
> implemented bck in 2008. Since then yum has changed some minor file naming
> conventions and otherwise altered the "standard" (but actually de facto)
> rpm-metadata format slightly.
> Wouldn't be hard to fix, is on my todo++ list, but there's been zero
> interest in using rpmrepo so far, hence its a low priority.
> You know where http://launchpad.net/rpm blueprints are.
> 73 de Jeff
Received on Wed Feb 23 20:04:31 2011