Bug 36238 - adding ruby-gettext to portage
|
Bug#:
36238
|
Product: Gentoo Linux
|
Version: 1.4
|
Platform: All
|
|
OS/Version: All
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: ruby@gentoo.org
|
Reported By: acid.punk@gmx.net
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: adding ruby-gettext to portage
|
|
Keywords: EBUILD
|
|
Status Whiteboard:
|
|
Opened: 2003-12-21 07:42 0000
|
This is a Native Language Support Library and Tools which are modeled after GNU
gettext package. It's an option for the new rbbr-0.5.1 also found here on
bugzilla.
Created an attachment (id=22523) [details]
ruby-gettext-0.5.3.ebuild
The SRC_URI for this package makes for some problems. Look at the commented URL
and you will know what I mean. Distrubiting the source with the Gentoo mirrors
is one solution. The new ebuild does that.
Thanks for contributing the ebuild. I didn't test it since I couldn't
fetch source tarball from the SRC_URI. However, I skimmed it and found
several minor things to fix.
* Will you agree to remove your name at the top of the ebuild? We
usually ask everyone to assign its copyright to Gentoo Technolgies,
Inc. It isn't compulsory but we would appreciate if you do so.
* The homepage says it could work not only with ruby 1.8 but also with
1.6. If you have some time, it would be nice to test it and change
>=dev-lang/ruby-1.8.0 to >=dev-lang/ruby-1.6.8. Otherwise ruby 1.6
users won't have the benefit of your ebuild ;-)
* (along with the point above) racc is included into ruby 1.8, so if
you force the dependencies to ruby 1.8, dev-ruby/racc isn't needed.
If you are going to add dev-lang/ruby-1.6*, it will be required.
(You may write something like DEPEND="|| ( >=dev-lang/ruby-1.8.0
( =dev-lang/ruby-1.6* dev-ruby/racc ) )" to express it)
* If the source has additional documents, you might want to add them
using dodoc (If there isn't any, it's okay. I'm asking it simply
because I don't have the source tarball).
If you rewrite the ebuild regarding my comments, please reattach it
here.
Please see http://article.gmane.org/gmane.linux.gentoo.devel/11417/ for the
copyright. Even though ruby 1.8 includes racc ruby-gettext seems to need the
seperate racc package since it check for the /usr/bin/racc executable which
isn't distributed with ruby 1.8. So I made it simply depend on dev-lang/ruby
and dev-ruby/racc. About the docs: there are some, but only in rd and some
samples to. No idea if this is so usefull, although documentation would be
nice. But also dodoc only handles files and not directories so I dont see an
easy way to add the docs/ and samples/ dirs to the ebuild, do you?
drobbins said so in the mail you pointed out but AFAIK the whole
thread didn't reach a certain conclusion (and he was the only one
saying so). Some devs are talking to a laywer about the copyright
issue, but I don't know what the outcome is.
I see why you put racc on DEPEND. When I can download the source
tarball I'll check them. As for documents dodoc isn't capable of
doing "-r" while dohtml supports useful flags like that, and I'm
waiting for Portage to include Bug #15193. For the time being, you may
`inherit ruby` and use erubydoc instead. (It doesn't take any
arguments but catches almost all docs and examples in addition to rd)
Created an attachment (id=24068) [details]
ruby-gettext-0.5.3.ebuild
Alright I corrected the copyright and use erubydoc now. erubydoc doesn't do a
very good job though.. the html/ dir is empty except for a .css file and there
also files like install.rb etc. which get gzipped and installed. Wouldn't a
'dodoc C* R*' be better?
Yesterday I was able to download the source and tried you ebuild. You
are right about adding racc as its dependencies. I added racc back to
the ebuild and committed to Portage.
Though erubydoc doesn't do much (I want to rewrite it anyhow), you
should have run `ruby makehtml.rb` inside docs directory to create
html files. In order to do so, you will be required rd2 from
dev-ruby/rdtools, so I added it to DEPEND, too. As for html directory,
I modified ruby.eclass a little to fix the problem.
Thanks again for your time and effort.