My experimentation with software collections has transformed into a big project where we will probably be building Perl (5.16, most likely) packages for RHEL 5 and 6 for deployment across dozens, perhaps hundreds, of servers.
Up until now, I've been building these packages by hand in a CentOS 6 VM on my laptop, but I realize to do it "right," I really need to set up a dedicated build environment, possibly using something like Koji.
Additionally, what do you think about making perl514 or perl516 packages available via EPEL? Once we have a build system in place, could we contribute our packages to EPEL or should we just set up our own public repository?
Your thoughts would be appreciated.
Dne 25.7.2012 19:11, Doran Barton napsal(a):
My experimentation with software collections has transformed into a big project where we will probably be building Perl (5.16, most likely) packages for RHEL 5 and 6 for deployment across dozens, perhaps hundreds, of servers.
Up until now, I've been building these packages by hand in a CentOS 6 VM on my laptop, but I realize to do it "right," I really need to set up a dedicated build environment, possibly using something like Koji.
Additionally, what do you think about making perl514 or perl516 packages available via EPEL? Once we have a build system in place, could we contribute our packages to EPEL or should we just set up our own public repository?
I am afraid that packages for software collections are prohibited by packaging guidelines: https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macr...
Vit
softwarecollections@lists.fedorahosted.org