Edit Info Other
Login

Diff for "FAQ"

Differences between revisions 5 and 6
Revision 5 as of 2008-07-23 12:58:26
Size: 3768
Comment:
Revision 6 as of 2008-11-09 13:46:15
Size: 4461
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
=== Frequently Asked Questions === = Frequently Asked Questions =
Line 6: Line 6:
==== What is RPM Fusion? ====
RPM Fusion is a repository of add-on packages for Fedora maintained by a group of volunteers. RPM Fusion is not a standalone repository, but an extension of Fedora. RPM Fusion distributes packages that have been deemed unacceptable to Fedora due to licensing or patent issues.
== RPM Fusion ==
Line 9: Line 8:
==== How do I use RPM Fusion? ==== === What is RPM Fusion? ===
RPM Fusion is a repository of add-on packages for Fedora and EL+EPEL maintained by a group of volunteers. RPM Fusion is not a standalone repository, but an extension of Fedora. RPM Fusion distributes packages that have been deemed unacceptable to Fedora.

=== How do I use RPM Fusion? ===
Line 12: Line 14:
==== Can I use RPM Fusion packages during the installation of Fedora? ====
Yes, as of Fedora Core 6, Anaconda (the Fedora installer) supports using external repositories during installation. See [[RPMFusionInAnaconda|Using RPM Fusion in Anaconda]] for more information.
=== Can I use RPM Fusion packages during the installation of Fedora? ===
Yes, Anaconda (the Fedora installer) supports using external repositories during installation. See [[RPMFusionInAnaconda|Using RPM Fusion in Anaconda]] for more information.
Line 15: Line 17:
==== What are the licensing or patent issues that make some packages unacceptable to Fedora? ====
As Fedora is officially affiliated with Red Hat, Inc. in the Fedora Project, Fedora is effectively bound by the same legal restrictions as Red Hat, as a US company, is bound by. This means in particular that software encumbered with US patents cannot be included. Also excluded is software covered by licenses which are incompatible with Red Hat's licensing policy, e.g. licenses which only permit non-commercial use. See Fedora list of [[http://www.fedoraproject.org/wiki/ForbiddenItems|forbidden items]].
=== Why doesn't the Fedora project ship the Software that RPM Fusion offers? ===
As Fedora is officially affiliated with Red Hat, Inc. in the Fedora Project, Fedora is effectively bound by the same legal restrictions as Red Hat, as a US company, is bound by. This means in particular that software encumbered with US patents cannot be included in Fedora.
Line 18: Line 20:
==== Does RPM Fusion distribute illegal software? ==== Fedora further only wants to ship software that is covered by Free and Open-Source-Software licenses; see Fedora's [[http://fedoraproject.org/wiki/Licensing|Licensing Guidelines]] and its [http://fedoraproject.org/wiki/Licensing#SoftwareLicenses|List of Good Licenses] for details.

=== Does RPM Fusion distribute illegal software? ===
Line 21: Line 25:
==== Why should I use the video drivers provided by RPM Fusion for my ATI and Nvidia cards? ==== === How can I trust that RPM Fusion will work with the Fedora project? ===
Most RPM Fusion developers are also actively involved in the Fedora project and make sure that RPM Fusion interacts properly with the distributions from Fedora. The contributors also do their best to maintain a the same quality as official Fedora packages.

RPM Fusion further doesn't want to compete with Fedora -- hence RPM Fusion normally does not ship any software that is acceptable in Fedora.

=== What Fedora versions do you support? ===

RPM Fusion ships packages for RHEL5 (and its derivatives like CentOS, ScientificLinux and other) and all current Fedora versions (including the development branch rawhide).

RPM Fusion follows the end-of-life policy of the respective "upstream" distributions. In practice this means that shortly after the upstream distribution goes EOL, shortly afterwards the corresponding RPM Fusion repository will go EOL, too. Usually the repositories will stay available for longer, but no new packages or package updates will be added to them and users are strongly encouraged to update to a non-EOL distro version. The repositories for EOLed distributions will sooner or later move to a archive page to make room for repositories for newer releases.

=== What architectures do you support? ===
We attempt to support all possible architectures, across all supported Fedora/EL versions. Currently for Fedora 9 and later these are i386, x86_64, ppc and ppc64; EL is limited to i386 and x86_64

=== How do I report a bug? ===
Please report all bugs using the [[https://bugzilla.rpmfusion.org/bugzilla/|Bugzilla]]. This includes bugs with RPMs as well as bugs related to infrastructure, such as this website.

=== I would like to see an RPM for package X. What should I do? ===
Place a [[Wishlist|request]] in the wiki and hopefully a maintainer will decide to pick it up. If however you wish to see an additional feature added to an ''existing'' package, please file a bug against it in [[https://bugzilla.rpmfusion.org/bugzilla/|Bugzilla]].

=== How can I contribute? ===
You can submit your own packages, do QA on existing submissions or help fix bugs . Please see the [[Contributors|contributors]] page for details.

== Packages ==

=== Why should I use the video drivers provided by RPM Fusion for my ATI and Nvidia cards? ===
Line 24: Line 53:
==== How can I trust that RPM Fusion will work with the Fedora project? ====
Most RPM Fusion developers are also actively involved in Fedora development and make sure that RPM Fusion tracks Fedora development, and also that the packages are of the same quality as official Fedora packages.
=== Why do I see i686 (or similar) RPMs in the i386 repositories? ===
Some RPMs are built from binary distributions because the source code is not available, although building from source is always preferred. In these cases, we have little or no control over how the binaries were compiled. So if they were compiled for i686, then they must be presented in an i686 RPM.
Line 27: Line 56:
==== What Fedora versions do you support? ====
RPM Fusion distribution versions follow the end-of-life policy of the respective "upstream" distributions. In practice this means that shortly after the upstream distribution goes EOL, shortly afterwards the corresponding RPM Fusion repository will go EOL too. Usually the repositories will stay available for quite a long time, but no new packages or package updates will be added to them and users are strongly encouraged to update to a non-EOL distro version.

==== What architectures do you support? ====
We attempt to support all possible architectures, across all supported Fedora versions. Currently these are i386, x86_64, ppc and ppc64.

==== Why do I see i686 (or similar) RPMs in i386? ====
Some RPMs are built from binary distributions because the source code is not available, although building from source is always preferred. In these cases, we have little or no control over how the binaries were compiled. So if they were compiled for i686, then they must be presented in an i686 RPM.

==== How can I contribute? ====
You can submit your own packages, do QA on existing submissions or help fix bugs. Please see the [[Contributors|contributors]] page for details.

==== How do I report a bug? ====
Please report all bugs using the [[https://bugzilla.rpmfusion.org/bugzilla/|Bugzilla]]. This includes bugs with RPMs as well as bugs related to infrastructure, such as this website.

==== I would like to see an RPM for package X. What should I do? ====
Place a [[Wishlist|request]] in the wiki and hopefully a maintainer will decide to pick it up. If however you wish to see an additional feature added to an ''existing'' package, please file a bug against it in [[https://bugzilla.rpmfusion.org/bugzilla/|Bugzilla]].

CategoryFAQ
Kernel-Modules are also build specifically for i586 or i686 -- hence the kmod packages are marked as i586 and i686, just like the kenrels in Fedora are.

Frequently Asked Questions

RPM Fusion

What is RPM Fusion?

RPM Fusion is a repository of add-on packages for Fedora and EL+EPEL maintained by a group of volunteers. RPM Fusion is not a standalone repository, but an extension of Fedora. RPM Fusion distributes packages that have been deemed unacceptable to Fedora.

How do I use RPM Fusion?

See Configuration.

Can I use RPM Fusion packages during the installation of Fedora?

Yes, Anaconda (the Fedora installer) supports using external repositories during installation. See Using RPM Fusion in Anaconda for more information.

Why doesn't the Fedora project ship the Software that RPM Fusion offers?

As Fedora is officially affiliated with Red Hat, Inc. in the Fedora Project, Fedora is effectively bound by the same legal restrictions as Red Hat, as a US company, is bound by. This means in particular that software encumbered with US patents cannot be included in Fedora.

Fedora further only wants to ship software that is covered by Free and Open-Source-Software licenses; see Fedora's Licensing Guidelines and its [http://fedoraproject.org/wiki/Licensing#SoftwareLicenses|List of Good Licenses] for details.

Does RPM Fusion distribute illegal software?

No. RPM Fusion only distributes packages which can be legally re-distributed.

How can I trust that RPM Fusion will work with the Fedora project?

Most RPM Fusion developers are also actively involved in the Fedora project and make sure that RPM Fusion interacts properly with the distributions from Fedora. The contributors also do their best to maintain a the same quality as official Fedora packages.

RPM Fusion further doesn't want to compete with Fedora -- hence RPM Fusion normally does not ship any software that is acceptable in Fedora.

What Fedora versions do you support?

RPM Fusion ships packages for RHEL5 (and its derivatives like CentOS, ScientificLinux and other) and all current Fedora versions (including the development branch rawhide).

RPM Fusion follows the end-of-life policy of the respective "upstream" distributions. In practice this means that shortly after the upstream distribution goes EOL, shortly afterwards the corresponding RPM Fusion repository will go EOL, too. Usually the repositories will stay available for longer, but no new packages or package updates will be added to them and users are strongly encouraged to update to a non-EOL distro version. The repositories for EOLed distributions will sooner or later move to a archive page to make room for repositories for newer releases.

What architectures do you support?

We attempt to support all possible architectures, across all supported Fedora/EL versions. Currently for Fedora 9 and later these are i386, x86_64, ppc and ppc64; EL is limited to i386 and x86_64

How do I report a bug?

Please report all bugs using the Bugzilla. This includes bugs with RPMs as well as bugs related to infrastructure, such as this website.

I would like to see an RPM for package X. What should I do?

Place a request in the wiki and hopefully a maintainer will decide to pick it up. If however you wish to see an additional feature added to an existing package, please file a bug against it in Bugzilla.

How can I contribute?

You can submit your own packages, do QA on existing submissions or help fix bugs . Please see the contributors page for details.

Packages

Why should I use the video drivers provided by RPM Fusion for my ATI and Nvidia cards?

This is described in the RPM Fusion Switcher page.

Why do I see i686 (or similar) RPMs in the i386 repositories?

Some RPMs are built from binary distributions because the source code is not available, although building from source is always preferred. In these cases, we have little or no control over how the binaries were compiled. So if they were compiled for i686, then they must be presented in an i686 RPM.

Kernel-Modules are also build specifically for i586 or i686 -- hence the kmod packages are marked as i586 and i686, just like the kenrels in Fedora are.

FAQ (last edited 2024-02-03 21:08:51 by Sérgio Basto)