Anyone know if it's possible for the gentoo ebuild for ruby to include ri and generate the documentation?
Charles Comstock
On ./configure.. add --enable-install-doc
that will build and install ruby documentation.
--David Ross
···
--- Charles Comstock <cc1@cec.wustl.edu> wrote:
Anyone know if it's possible for the gentoo ebuild
for ruby to include
ri and generate the documentation?Charles Comstock
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Does this work for you?
env USE="doc ruby" emerge -va ruby
Regards,
Ed
···
On Sat, 28 Aug 2004 03:50:34 +0900, Charles Comstock <cc1@cec.wustl.edu> wrote:
Anyone know if it's possible for the gentoo ebuild for ruby to include
ri and generate the documentation?
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
David Ross wrote:
On ./configure.. add --enable-install-doc
that will build and install ruby documentation.
--David Ross
That doesn't make it part of the package. I know how to compile ruby on my own fine, I wanted to know how to do it through gentoo's build system and if anyone knew how that was supposed to work. If I'm typing in the ../configure manually then that doesn't really justify me using a package manager now does it?
Charles Comstock
···
--- Charles Comstock <cc1@cec.wustl.edu> wrote:
Edgardo Hames wrote:
···
On Sat, 28 Aug 2004 03:50:34 +0900, Charles Comstock <cc1@cec.wustl.edu> wrote:
Anyone know if it's possible for the gentoo ebuild for ruby to include
ri and generate the documentation?Does this work for you?
env USE="doc ruby" emerge -va ruby
Regards,
Ed
Thanks, but my use variable already has doc and ruby in it, so I'm thinking that doesn't enable it. Maybe I just need to go in and tweak the ebuild myself.
Charles Comstock
Charles Comstock <cc1@cec.wustl.edu> writes:
I wanted to know how to do it through gentoo's build system
and if anyone knew how that was supposed to work.
Have you tried to contact the maintainer of this ebuild ? Maybe he
could do something for that.
···
--
Éric Jacoboni, né il y a 1397084676 secondes
Thanks, but my use variable already has doc and ruby in it, so I'm
thinking that doesn't enable it. Maybe I just need to go in and tweak
the ebuild myself.
Apparently ri has a separate ebuild: emerge -av ri
Peter
Peter wrote:
Thanks, but my use variable already has doc and ruby in it, so I'm
thinking that doesn't enable it. Maybe I just need to go in and tweak
the ebuild myself.Apparently ri has a separate ebuild: emerge -av ri
Peter
But is that actually the up to date ri or is that the old school ri that used to be packaged seperately?
Charles Comstock
But is that actually the up to date ri or is that the old school ri that
used to be packaged seperately?
Right. It's the old one. The ruby ebuild does install a ri (and calls it
ri18), but it does not generate the docs. Since the ebuild does not
reference the --enable-install-doc flag, I expect it can't generate the
docs unless you add the flag to the ebuild yourself.
Peter
Why the @&%# do these damn packages not install Ruby properly? Is it
malice, incompetence, ignorance, stretched resources, or just out of
date? I don't even use the damn things, but they annoy the absolute
crap out of me with all the "support" issues they create!
(Not that I mind people looking to have problems solved in this forum
-- any person with any problem is welcome.)
Gavin
···
On Saturday, August 28, 2004, 11:52:29 AM, Peter wrote:
But is that actually the up to date ri or is that the old school ri that
used to be packaged seperately?
Right. It's the old one. The ruby ebuild does install a ri (and calls it
ri18), but it does not generate the docs. Since the ebuild does not
reference the --enable-install-doc flag, I expect it can't generate the
docs unless you add the flag to the ebuild yourself.
It looks like bug #62003 was submitted to bugs.gentoo.org yesterday
regarding this issue. I added a comment with the suggestion to add
"--enable-install-doc" when the "doc" use flag is set.
Henry.
···
On Sat, Aug 28, 2004 at 10:52:29AM +0900, Peter wrote:
Right. It's the old one. The ruby ebuild does install a ri (and calls it
ri18), but it does not generate the docs. Since the ebuild does not
reference the --enable-install-doc flag, I expect it can't generate the
docs unless you add the flag to the ebuild yourself.
Why the @&%# do these damn packages not install Ruby properly? Is it
malice, incompetence, ignorance, stretched resources, or just out of
date? I don't even use the damn things, but they annoy the absolute
crap out of me with all the "support" issues they create!(Not that I mind people looking to have problems solved in this forum
-- any person with any problem is welcome.)Gavin
Sorry I wasn't so much trying to get support here as validating that I wasn't just doing something stupid. I submitted the bug report, so hopefully it should be fixed. I think in this case it was simply a matter that the build cycle had been setup on early 1.8.0 and they had just copied and modified the ebuild for each version after. I mean it does have 1.8.2preview2 as the ebuild right now, I guess no one realized about the docs thats all.
Charles Comstock
Henry T. So Jr. wrote:
It looks like bug #62003 was submitted to bugs.gentoo.org yesterday
regarding this issue. I added a comment with the suggestion to add
"--enable-install-doc" when the "doc" use flag is set.
Dunno if it helps, but I had the same problem when I installed ruby-cvs, and apparently in the ebuild, the --enable-install-doc was commented with a statement saying there was problem using it:
# disable install-doc because of yaml/parser
I think this was related to an old CVS version and it has never been corrected since.
Frederick Ros
Henry T. So Jr. wrote:
> It looks like bug #62003 was submitted to bugs.gentoo.org yesterday
> regarding this issue. I added a comment with the suggestion to add
> "--enable-install-doc" when the "doc" use flag is set.
Dunno if it helps, but I had the same problem when I installed ruby-cvs, and apparently in the ebuild, the --enable-install-doc was commented with a statement saying there was problem using it:
# disable install-doc because of yaml/parser
I think this was related to an old CVS version and it has never been corrected since.
Frederick Ros