Differences between version 6 and predecessor to the previous major change of FedoraExtras.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 6 | Last edited on Saturday, July 3, 2004 7:41:06 pm | by AlastairPorter | Revert |
| Older page: | version 5 | Last edited on Thursday, April 8, 2004 5:42:41 am | by BrianBober | Revert |
@@ -1,20 +1,12 @@
-Located at:
[www.fedora.us|http://www.fedora.us/]
+Located at [www.fedora.us|http://www.fedora.us/]
-Because of licensing issues
, certain
packages including but not limited to mplayer, xine and xmms-mp3 cannot be placed in Fedora Extras. You might therefore want to give [rpm.livna.org|RPMLivnaOrg] a try
.
+As the name suggests
, the FedoraExtras project provides extra
packages for your FedoraCore installation that don't come with it by default
.
-From
[Fedora terminology:
|http://fedora.redhat.com
/participate
/terminology.html
]
+It is accessable via
[Yum] or [apt|AptForRpm]. See instructions on [their site
|http://www.
fedora.us
/wiki
/FedoraSources
]
-Fedora Extras are sets
of packages that augment FedoraCore
but do
not replace Fedora Core component packages. These packages
, like all packages that are part of The FedoraProject, must conform to the legal requirements of the project
and conform
to the Fedora Extras policies
.
+Because
of licensing issues, certain
packages including
but not limited to mplayer
, xine
and xmms-mp3 cannot be placed in FedoraExtras. You might therefore want
to give [rpm.livna.org|RPMLivnaOrg] a try
.
-"Fedora Extras"
is a category that applies
to multiple repositories. For example, someone might wish to build a set of
packages for high performance computing use and call it "Fedora Extras HPC"; it would be one of the Fedora Extras.
-
-Packages in Fedora Extras must be built entirely
from software meeting the OpenSource guidelines; furthermore, packages in Fedora Extras must be buildable only using software which is in Fedora Core or Fedora Extras. Fedora Extras need to be kept roughly up to date with Fedora Core releases
and must be signed with
the package's key rather than the Fedora key. Packages in Fedora Extras are expected to release updates to fix security issues. RHN has the option to carry Fedora Extras content.
-
-RedHat will provide build systems, CVS repositories, ftp and web services, and possibly other facilities needed by the Fedora Extras packages.
-
-Packages in Fedora Extras should avoid conflicts with other packages in Fedora Extras to the fullest extent possible. Packages in Fedora Extras must not conflict with packages in Fedora Core. It is possible to have many Fedora Extras packages under the umbrella of a single Fedora Extras project.
-
-The technical committee is responsible for accepting packages into Fedora Extras based on the technical merits of the package and the proposed package's maintainer. The technical committee is the combination of the steering committee and advisory committee with each individual getting a single vote.
+It
is considered
a bad idea
to mix
packages from FedoraExtras
and the BigFive
----
-See FedoraProject, FedoraCore, FedoraAlternatives and FedoraLegacy
+See also:
FedoraProject, FedoraCore, FedoraAlternatives and FedoraLegacy
