The official CentOS distribution is a direct rebuild of the packages supplied by the upstream provider (RedHat). To get officially included in CentOS, you would need to be officially included in RedHat Enterprise Linux.

There are other options, such as getting included in the EPEL repository, which many people use to find additional packages to use with CentOS. You can view a list of the different repositories that work with CentOS here: http://wiki.centos.org/AdditionalResources/Repositories

❧ Brian Mathis

On Tue, Sep 10, 2013 at 11:40 AM, Sancho Lerena slerena@gmail.com wrote:

Hi everybody

First at all, sorry if this mailing list is not the appropriate for the question I have.

I'm the project leader of Pandora FMS; a monitoring software with GPL licence. I want to include the packages officially in centos (our main distro) and we already have the RPM's created and even a customized centOS modified distro in CD (thanks to kickstart and livecd tools). The question is, how will be the best way to incorporate our packages to the official distro?.

Thanks a lot for your time.

Un saludo,

    Sancho Lerena
    Pandora FMS, the flexible monitoring system
    http://pandorafms.org

---

CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

On 09/10/2013 04:40 PM, Sancho Lerena wrote:

First at all, sorry if this mailing list is not the appropriate for the question I have.

I'm the project leader of Pandora FMS; a monitoring software with GPL licence. I want to include the packages officially in centos (our main distro) and we already have the RPM's created and even a customized centOS modified distro in CD (thanks to kickstart and livecd tools). The question is, how will be the best way to incorporate our packages to the official distro?.

Thanks a lot for your time.

This is the best mailing list for the question!

Can you point me at the rpms set you have at the moment ?

Also, 1) Are you hoping to target CentOS-Extras or do we need CentOS-Plus content ( i.e. is the package set completely non-overlapping with distro components ? )

2) The ISO you have there, does that change the installer behaviour in anyway ?

3) Is everything open source, compatible with the gplv2 ?

4) Do you rely on any other repo apart from CentOS-Base in order to build the rpms ?

Regards,

- - KB

- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

On Tue, Sep 10, 2013 at 9:04 AM, Farkas Levente lfarkas@lfarkas.org wrote:

On 09/10/2013 04:58 PM, Dave Johansen wrote:

...

http://rhn.redhat.com/errata/RHEA-2013-1226.html

devtoolset 2.0 was just released. Any chance we can get a build of it like the previous one?

it's still beta. anyway unfortunately 2.0 can't be build without binary rpm from rh so imho centos no longer can release 2.0 rpms.

That ERRATA is declaring that 2.0 is officially released (no longer just a beta) and the source RPMs are available here: http://ftp.redhat.com/pub/redhat/linux/enterprise/6Workstation/en/RHDevTools...

Am 26.09.2013 21:55, schrieb Jeff Gustafson:

I tried to compile some of the src.rpm's. It almost seems like they were using a Fedora box to compile the packages. The missing packages listed in the spec file are readily available on Fedora. Even the requirements for 'java >= 1.6.0' seemed to be satisfied on Fedora, but not RHEL. Are

Sorry for bringing this old thread up again, but for 'java >= 1.6.0' there are at least seven rpms in RHEL6 which satisfy that dependency. Or didn't I understand rright?

VG Rainer