Hello,
I was searching around a bit on the wiki and in list archives, but without any luck, so asking here.
He have several dozens of packages (mostly Ruby packages) prepared for our projects (Foreman, Katello, Pulp, Candlepin and few others). We already submitted and maintain some packages in Fedora, but our plan is to make our SPEC files compliant and start submitting all of them over the time.
The only issue is we need to keep our SCL macros (maily scl_prefix and few others) in our packages, because as you can see [1] it is pretty inconvenient to maintain those as a separate branches or patch sets (the scl_prefix is spread all over the SPEC file causing lots of conflicts).
I have been trying to find some information about SCL macros and if these are allowed in SPEC files in Fedora. We are willing to submit packages and maintain them of course, but before we start pushing review request, I would like to be clear if this is not prohibited from Fedora.
Of course, I understand SCL is not allowed as described here [2], but the issue I am writing about is only about having some macros in our SPEC files which are left unexpanded in Fedora Koji of course.
The main drawback is readability which is worse in this case. On the other hand, if unexpanded macros are not prohibited, SCL should make no difference. If they are, I'd like to start conversation about possibility to make an exception for this case.
I would like to read your opinions about that and if there is no document allowing these macros, I'd like to ask to help me to create one. We need an official document which can be used during reviews in case there are doubts about the SCL macros.
Thank you for your help.
[1] - http://bit.ly/13rzLFF (example of a SCL enabled Ruby package) [2] - https://fedoraproject.org/wiki/SoftwareCollections
Le 02/08/2013 09:32, Lukas Zapletal a écrit :
Hello,
The only issue is we need to keep our SCL macros (maily scl_prefix and few others) in our packages, because as you can see [1] it is pretty inconvenient to maintain those as a separate branches or patch sets (the scl_prefix is spread all over the SPEC file causing lots of conflicts).
Explained here : https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macr...
So this is acceptable.
I also have some of my spec adapted for SCL in rawhide, because the changes are quite minor. Mostly because I don't want to loose my work.
I hope we'll be able in the (near) future to build packages in EPEL for/using RHSCL. In this case, the SCL will be in a specific branch (and the fedora spec will be clean for more legibility).
Remember, there is no rule to use the same spec in all branches ;)
Remi.
On Fri, Aug 02, 2013 at 10:04:59AM +0200, Remi Collet wrote:
Explained here : https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macr...
This is *exactly* I was searching for :-)
I hope we'll be able in the (near) future to build packages in EPEL for/using RHSCL. In this case, the SCL will be in a specific branch (and the fedora spec will be clean for more legibility).
Yes, this would be awesome and could bring EPEL little bit "back to life" for some stacks.
Thank you.
packaging@lists.fedoraproject.org