RFC regarding rpmfusion-{non,}free-release and F11

[Till Maas]

On Di Mai 12 2009, Thorsten Leemhuis wrote:

> - mark the repo files for the initial rpmfusion-{non,}free-release-11
> package as %config instead of %config(noreplace). That way we make sure
> the new repo files get into the right place and actually used by yum; if
> the old repo files had been modified then they get saved as .rpmsave
> files and users would need to merge those changes into the new files
> (but they would have to do that anyway, even if the files would be
> marked as %config(noreplace))

> Does that sound like a plan? Yes, I'm well aware that it has some
> downsides, but afaics it's the one that works painlessly for most
> people. Or am I missing a better way?

Imho repo config files must not be marked as %config without noreplace, 
because they may contain vital options that may mess up the whole system if 
they are overwritten, e.g. if options like excludepkgs, priority or protect 
are removed.

In the fedora.repo file from F10, there is $basearch used in the URL of the 
gpgkey, maybe it is also possible to use $releasever there, so that it is 
possible to use the same gpgkey URL for several Fedora Releases, e.g.
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-$releasever

Regards
Till
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.rpmfusion.org/pipermail/rpmfusion-developers/attachments/20090513/dc72eae2/attachment.bin