Hi,
I noticed that the old ruby guidelines[0] and the new ruby guidelines[1] use different macro names, for example gemname and gem_name. Since the old guidelines need to be used for several years in EPEL, I propose to adjust the old guidelines to the new guidlines as much as possible:
- use consistent macro names - define macros provided in rubygems-devel in F17+ in spec files according to the old guidelines
Are there any general objections? Otherwise I will prepare a Packaging Draft with above changes.
Regards Till
[0] https://fedoraproject.org/wiki/Packaging:Old_Ruby [1] https://fedoraproject.org/wiki/Packaging:Ruby
Dne 27.6.2012 15:07, Till Maas napsal(a):
Hi,
I noticed that the old ruby guidelines[0] and the new ruby guidelines[1] use different macro names, for example gemname and gem_name. Since the old guidelines need to be used for several years in EPEL, I propose to adjust the old guidelines to the new guidlines as much as possible:
- use consistent macro names
- define macros provided in rubygems-devel in F17+ in spec files according to the old guidelines
Are there any general objections? Otherwise I will prepare a Packaging Draft with above changes.
Regards Till
[0] https://fedoraproject.org/wiki/Packaging:Old_Ruby [1] https://fedoraproject.org/wiki/Packaging:Ruby -- packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
Hi Till,
I am not completely sure what should be actual result of the changes, so I am going to throw in just a few notes:
* The macro names for packaging rubygems, which are used in F17, could be used in all Fedoras, since they were backported into the previous releases. * I'd love to see them also in RHEL [1], but that is not up to me unfortunately. * On one hand, I'd love to see the old guidelines more aligned with the current guidelines, but I am afraid we cannot avoid confusion, so I am not sure that the change is worth of it.
Vit
packaging@lists.fedoraproject.org