EPEL/it

In other languages: English (en) español (es) italiano (it) 日本語 (ja) português do Brasil (pt-br) 中文（中国大陆） (zh-cn) [edit]

This page is NOT completely translated yet.
Questa pagina non è stata ancora completamente tradotta.

Extra Packages for Enterprise Linux (EPEL)

Benvenuti nella home dell'EPEL Special Interest Group.

Cosa è Extra Packages for Enterprise Linux (o EPEL)?

'Extra Packages for Enterprise Linux' (o EPEL) è un gruppo speciale di utenti (Fedora Special Interest Group) che si interessa di creare, mantenere e gestire pacchetti RPM addizionali di alta qualità per Enterprise Linux, includendo, ma non limitato, Red Hat Enterprise Linux (RHEL), CentOS e Scientific Linux (SL).

I pacchetti EPEL sono solitamente basati sulla loro controparte in Fedora e non saranno mai in conflitto o un rimpiazzo con quelli base per le distribuzioni Enterprise Linux. EPEL usa parte della stessa infrastruttura usata per Fedora, inclusi buildsystem, bugzilla instance, update manager, mirror manager ed altro.

Per saperne di più su EPEL, seguire le seguenti pagine:

• EPEL FAQ

• About EPEL

• Politiche e Linee guida di EPEL

What packages and versions are available in EPEL?

You can take a look on any of the available EPEL mirrors from our mirror list

Alternately, you can browse the package set using repoview:

• EPEL 6: i386, x86_64, ppc64, sources
• EPEL 5: i386, x86_64, ppc, sources

How can I use these extra packages?

EPEL has an 'epel-release' package that includes gpg keys for package signing and repository information. Installing this package for your Enterprise Linux version should allow you to use normal tools such as yum to install packages and their dependencies. By default the stable EPEL repo is enabled, there is also a 'epel-testing' repository that contains packages that are not yet deemed stable.

NOTE for RHN users.
You need to also enable the 'optional' repository to use EPEL packages as they depend on packages in that repository. This can be done by enabling the RHEL optional subchannel for RHN-Classic. For certificate-based subscriptions see RHEL Deployment Guide

If you are running an EL6 version, please visit here to get the newest 'epel-release' package for EL6: The newest version of 'epel-release' for EL6

If you are running an EL5 version, please visit here to get the newest 'epel-release' package for EL5: The newest version of 'epel-release' for EL5

You can verify these packages and their keys from the Fedora project's keys page: https://fedoraproject.org/keys

History and background of the project

The EPEL project was born when Fedora maintainers realized that the same infrastructure that builds and maintains packages would be great to also maintain add on packages for Enterprise Linux. Much of the early need was driven by what Fedora infrastructure needed on the RHEL machines that built and maintained Fedora. From there things have grown to a large collection of varied packages. See our history and Philosophy page for more information.

How can I contribute?

The EPEL SIG is always looking for interested folks to help out. We always need package maintainers, qa/testers, bug triagers, marketing and documentation writers. Please see our Joining EPEL page for more information on how to join the SIG.

Communicating with the EPEL SIG

There are many ways to communicate with the EPEL SIG and it's members:

• The #epel^[?] IRC channel on irc.freenode.net offers real-time support for EPEL users and developers.

• The epel-devel-list is for general developer and SIG discussion.

• The epel-announce mailing list is a low volume mailing list for only important announcements.

• The epel-package-announce list is a list that gets information about package updates as they happen in the stable repository.

• If you find a bug in a EPEL maintained package, please report it to https://bugzilla.redhat.com/ under the "Fedora EPEL" product.

• The EPEL SIG meets every week in the #fedora-meeting^[?] channel at 20:30 UTC. Feel free to join us! Logs of past meetings can be found at: http://meetbot.fedoraproject.org/teams/epel/