Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Request: Inclusion of a ruby template file https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180066 ------- Additional Comments From ville.skytta@xxxxxx 2006-02-05 09:01 EST ------- (In reply to comment #4) > Well, I agree with you, but concerning the License tag I like to put some kind > of comment into the file to clarify the license issue. Or do you suggest to > correct this in case someone commits a new package? I don't think there's any need for clarification/correction. > I am not sure what the reasoning behind this python-abi = %(...) is, but what > I need to check is, that ruby is >= 1.8 Actually, if it's like in perl/python, one needs to require a version of ruby-libs that the package works with, including ruby-libs loading extensions from the versioned install dirs. >= 1.8 is probably incorrect, because I guess ruby 2.0 won't load extensions from the 1.8 dirs. The ruby-libs package could provide for example ruby(abi) = 1.8, and in that case the scriptlet from your original specfile would be ok I think (obviously changed to require ruby(abi) = ...). Currently, I think the best that can be done is to use dir based dependencies, %{ruby_sitelib} for noarch, %{ruby_sitearch} for non-noarch. I've committed the template from comment 7 to CVS with the dir based deps and other minor modifications, please submit further changes as diffs against the fedora-rpmdevtools in the fedora (note: not extras) repository, http://cvs.fedora.redhat.com/viewcvs/fedora-rpmdevtools/?root=fedora I wonder if a 'export CFLAGS="$RPM_OPT_FLAGS"' should be put to the spec template's %build section (to honor $RPM_OPT_FLAGS like in perl/python). Also, is it possible to include something better than the comments in %files, for example stuff like in the perl spec template? -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
