On Wed, 2008-10-29 at 14:26 +0100, Michael Schwendt wrote:
On Wed, 29 Oct 2008 14:03:08 +0200, Jonathan Dieter wrote:
> I would love to see the official rpmfusion repositories become
> presto-enabled, but it would take some love from those who understand
> the build system.
What are the exact requirements?
Whichever machine builds the deltarpms needs loads of RAM (mainly for
the really big rpms). Specifically, you need (uncompressed_size_of_rpm
Other than that, not much
Are presto-utils and deltarpm available for the target platform,
I know deltarpm is available for EL-5, and if presto-utils isn't, I'll
push it out.
The README in presto-utils reads as if all that is needed is the
path to a normal rpms repository (i.e. the parent of the repodata dir).
Yes, though if you're doing rpmfusion-free and rpmfusion-updates-free,
ATM that path needs to be a parent directory of both. In the test
repositories, I kludge it by making a rpmfusion+updates-free that
contains symlinks to rpmfusion-free and rpmfusion-updates-free. (If
that's not clear, check out the directory layout in
and you should see what I mean.)
Updating presto repositories is just like creating them for the
It shouldn't be difficult to add another module to the
See bottom 20 lines of
where modules like RepoPrune, RepoView, RepoBuild (createrepo) are
executed. They have access to configuration parameters so they can
construct a list of repository paths. A Presto or PrestoBuild module
would work similarly.
Yes, that looks *way* simpler than the proposed method in Fedora. I've
got some time tomorrow; I'll see what I can come up with.