Hi,
This is not a fully backed idea right now, but at least something I
try to figure out.
With the introduction of chromium freeworld and others packages in the
wish list, I think there is a need for a better way to handle theses
cases.
The fundamental problem with freeworld packages is that they need to
be in-sync with their fedora counterpart.
This is more or less relevant depending if the freeworld package
supersede (like in freetype) or complement (like in chromium-libs) the
fedora one. At least, it is expected that the same "patch level" is
used in both versions.
If the maintainer is the same in both cases, it's probably best,
because we expect the update to be done in both side at the same time.
Now when it's not the case, it's somehow an ungrateful task, because
it requires a maintainer to keep track of another maintainer activity.
(hopefully they can talk each others).
What I would suggest instead is the following:
Instead of having a normal git repository in the rpmfusion version, we
set an information that we will track the fedora package, and apply a
modification to it (rename to -freeworld, set global freeworld 1, use
unmodified tarball, etc).
This task can be implemented in rfpkg-minimal which in turn would call
fedpkg-minimal to fetch the git, then modify the content to create a
foo-freeworld.src.rpm to be built.
The unmodified tarball can be uploaded to the rpmfusion lookaside
cache, then it would requires the fedora maintainer cooperation so
only a minimal changes would be required to turn the package into a
freeworld version.
For the implementation details, I don't know if it would be possible
to use a git sub-module from the rpmfusion git to reference the fedora
git, or if rfpkg-minimal can just fetch the latest fedora branch of
the current rpmfusion branch (without any use of fedpkg verrel or
giturl).
Anyone to pick this task ?
At least looking into rfpkg-minimal modification doesn't requires any
access to the infra.
Thx
--
-
Nicolas (kwizart)