Am 28.01.2015 um 07:07 schrieb Philip Keogh: Hi Philip,> There's a .spec file that the author ran through mock on EL7: > https://github.com/mckern/carbon/blob/rpm_spec/rpm_spec/carbon.specBy author you mean the author of the RPM?> (If you need to know how to generate an RPM from a .spec see > https://fedoraproject.org/wiki/How_to_create_an_RPM_package )Ta.> You can also likely use this Fedora tree: > http://pkgs.fedoraproject.org/cgit/graphite-web.git/tree/That's the one I already found. But I wasn't sure in which state this was. So you mean this is "stable"? Is this the one which will some day show up in EPEL? What is the process for this? Sorry for the many questions. But I just started to dive deeper into CentOS- and RPM-land and there's a lot to learn. Cheers, Shorty -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20150128/3cb80ced/attachment-0001.sig>
On Tue, Jan 27, 2015 at 10:23 PM, Markus "Shorty" Uckelmann <shorty at koeln.de> wrote:> Am 28.01.2015 um 07:07 schrieb Philip Keogh: >> You can also likely use this Fedora tree: >> http://pkgs.fedoraproject.org/cgit/graphite-web.git/tree/ > > That's the one I already found. But I wasn't sure in which state this > was. So you mean this is "stable"? Is this the one which will some day > show up in EPEL? What is the process for this? > > Sorry for the many questions. But I just started to dive deeper into > CentOS- and RPM-land and there's a lot to learn. > > Cheers, Shorty >For EPEL's process, see their web site (which also contains a procedure for getting package updates created and finding the maintainer of a package that you are interested in): https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies In the case of graphite-web, that data is here: https://admin.fedoraproject.org/pkgdb/package/graphite-web/ The package has been approved for inclusion in EPEL 7 but was not yet built/released and is not in testing. (as per guidelines minimum of 2 weeks in testing prior to release) The only person who can give you their plans for a specific package is the point of contact package administrator, jsteffan in this case. Typically these things go faster if someone takes the initiative in testing an updated .spec and package, sending the SRPM to the maintainer instead of a request for them to drop what they are doing to start a project for your needs. If you are prioritizing "stability" CentOS 7 seems like a dubious choice to begin with though.
Am 28.01.2015 um 08:08 schrieb Philip Keogh:> For EPEL's process, see their web site (which also contains a > procedure for getting package updates created and finding the > maintainer of a package that you are interested in): > https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies > > In the case of graphite-web, that data is here: > https://admin.fedoraproject.org/pkgdb/package/graphite-web/ > > The package has been approved for inclusion in EPEL 7 but was not yet > built/released and is not in testing. (as per guidelines minimum of 2 > weeks in testing prior to release) > > The only person who can give you their plans for a specific package is > the point of contact package administrator, jsteffan in this case. > Typically these things go faster if someone takes the initiative in > testing an updated .spec and package, sending the SRPM to the > maintainer instead of a request for them to drop what they are doing > to start a project for your needs.Thanks a lot for taking the time to answer my "nosy" questions.> If you are prioritizing "stability" CentOS 7 seems like a dubious > choice to begin with though.That's as always "in the eye of the beholder" ;) Cheers, Shorty