Is it possible to have an alias to a rubygem rpm or are there exceptions to the rule that it must have the rubygem- prefix.
I ask in relation to two packages.
The first is rubygem-asciidoctor.
This package provides both a Ruby library and a system executable. It's a drop-in replacement for the asciidoc package (in most common cases). People are expecting to be able to install an RPM named "asciidoctor", just a few characters extra from "asciidoc" and get the RPM. Instead, they have to be aware it's a rubygem and type "rubygem-asciidoctor". Is it possible to have an alias package in this case like in Debian where it will install rubygem-asciidoctor when you request asciidoctor?
The second case is a new package I'm submitting named Awestruct. This is not a Ruby library at all, but strictly a system executable. Do I have to name it "rubygem-awestruct" or can I name it simply "awestruct".
Thanks,
-Dan
On Thu, Mar 28, 2013 at 3:11 PM, Dan Allen dan.j.allen@gmail.com wrote:
Is it possible to have an alias package in this case like in Debian where it will install rubygem-asciidoctor when you request asciidoctor?
I would love to see this for some other utility gems as well, like "gem2rpm" or "puppet-lint". It would be nice if we allowed a simple "Provides:" for these cases.
- Ken
Aha! That's exactly what I was looking for.
I found an example that fits very close to my use case (from the Java packages).
The maven-resources-plugin declares that it provides maven2-plugin-resources [1]. Perhaps the latter is an old name, or something people tend to call it. Either way, this works:
yum install maven2-plugin-resources
That would mean that if I had:
Provides: asciidoctor
or
Provides: awestruct
Then these would work:
yum install asciidoctor yum install awestruct
Then I would be a happy packager :)
-Dan
[1] http://pkgs.fedoraproject.org/cgit/maven-resources-plugin.git/tree/maven-res...
On Thu, Mar 28, 2013 at 3:55 PM, Ken Dreyer ktdreyer@ktdreyer.com wrote:
On Thu, Mar 28, 2013 at 3:11 PM, Dan Allen dan.j.allen@gmail.com wrote:
Is it possible to have an alias package in this case like in Debian where it will install rubygem-asciidoctor when you request asciidoctor?
I would love to see this for some other utility gems as well, like "gem2rpm" or "puppet-lint". It would be nice if we allowed a simple "Provides:" for these cases.
- Ken
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
On Thu, Mar 28, 2013 at 5:55 PM, Ken Dreyer ktdreyer@ktdreyer.com wrote:
On Thu, Mar 28, 2013 at 3:11 PM, Dan Allen dan.j.allen@gmail.com wrote:
Is it possible to have an alias package in this case like in Debian where it will install rubygem-asciidoctor when you request asciidoctor?
I would love to see this for some other utility gems as well, like "gem2rpm" or "puppet-lint". It would be nice if we allowed a simple "Provides:" for these cases.
If this is an accepted practice I would be willing to do this for puppet-lint.
Russell
Dne 28.3.2013 22:11, Dan Allen napsal(a):
Is it possible to have an alias to a rubygem rpm or are there exceptions to the rule that it must have the rubygem- prefix.
I ask in relation to two packages.
The first is rubygem-asciidoctor.
This package provides both a Ruby library and a system executable. It's a drop-in replacement for the asciidoc package (in most common cases). People are expecting to be able to install an RPM named "asciidoctor", just a few characters extra from "asciidoc" and get the RPM. Instead, they have to be aware it's a rubygem and type "rubygem-asciidoctor". Is it possible to have an alias package in this case like in Debian where it will install rubygem-asciidoctor when you request asciidoctor?
You you already found out, you can use Provides: for that.
However there are other options as well. If there is possible to split the application and the library part (i.e. the rubygem), there would be possible to provide either the application or the rubygem as as subpackage.
Note, that you can always do "yum install /usr/bin/asciidoctor" and you don't care what package it provides. At the end, you probably know what executable you want to use.
The second case is a new package I'm submitting named Awestruct. This is not a Ruby library at all, but strictly a system executable. Do I have to name it "rubygem-awestruct" or can I name it simply "awestruct".
Well, if that is not Ruby library, then it is application, therefore you can apply the application guidelines [1]. Note that there is also following note in the ruby naming guidelines: "Application packages that mainly provide user-level tools that happen to be written in Ruby must follow the general NamingGuidelines instead."
Vít
[1] https://fedoraproject.org/wiki/Packaging:Ruby#Applications
ruby-sig@lists.fedoraproject.org
-
Dan Allen -
Ken Dreyer -
Russell Harrison -
Vít Ondruch