[#2139] Best way to install ri documentation — Dave Thomas <dave@...>
Folks:
On Monday, January 5, 2004, 2:29:57 AM, Dave wrote:
Hi,
Perhaps make it available for mirrors and save ruby-lang's bandwidth?
Hi,
So, I'm thinking about doing the following? Is this OK with everyone?
Hi,
On Tue, 6 Jan 2004 00:47:41 +0900
On Mon, 12 Jan 2004 23:30:52 +0900
On Tue, Jan 13, 2004 at 12:01:38AM +0900, Dave Thomas wrote:
Hi, Dave,
Hi,
Hi, daz,
On Tuesday, 6 January 2004 at 15:02:50 +0900, NAKAMURA, Hiroshi wrote:
[#2163] Occasional --enable-pthread hangs... — Nathaniel Talbott <nathaniel@...>
First of all, thanks so much to all those that have helped with
On Jan 5, 2004, at 21:49, Nathaniel Talbott wrote:
[#2186] Absolute paths in shebang lines? — "J.Herre" <jlst@...>
What would the reaction be to reconsidering the following proposal?
[#2194] File.readable_world? and File.writable_world? — Ian Macdonald <ian@...>
Hello,
On Fri, Jan 09, 2004 at 06:02:07PM +0900, Ian Macdonald wrote:
On Fri 09 Jan 2004 at 23:10:02 +0900, Eivind Eklund wrote:
Hi,
On Sun 11 Jan 2004 at 00:47:33 +0900, Yukihiro Matsumoto wrote:
Hi,
On Sun 11 Jan 2004 at 21:40:22 +0900, Yukihiro Matsumoto wrote:
Hi,
On Mon 12 Jan 2004 at 10:31:52 +0900, Yukihiro Matsumoto wrote:
Hi,
On Mon 12 Jan 2004 at 22:36:16 +0900, Yukihiro Matsumoto wrote:
On Mon 12 Jan 2004 at 10:31:52 +0900, Yukihiro Matsumoto wrote:
On Sun 11 Jan 2004 at 00:47:33 +0900, Yukihiro Matsumoto wrote:
[#2211] xxx_init_copy — Dave Thomas <dave@...>
I notivce that there're a bunch of new xxx_init_copy methods: RDoc is
Hi,
Hi,
Hi,
Hi,
[#2216] ruby aborts in data-handling applications — xsdg <xsdg@...>
I reported a similar bug about 2 or 3 months ago. The problem seemed to go
Hi,
I've finally found a combination that will reliably segfault. Since my first post on this topic, I've switched the backend from BDB to GDBM.
Hi,
On Mon, Jan 19, 2004 at 11:32:59AM +0900, nobu.nokada@softhome.net wrote:
[#2225] Fwd: [ruby-cvs] ruby: * file.c (test_wr, test_ww): New functions implementing new — Dave Thomas <dave@...>
On Mon 12 Jan 2004 at 23:38:29 +0900, Dave Thomas wrote:
[#2251] YAML_Unit_Tests failed — "NAKAMURA, Hiroshi" <nahi@...>
Hi,
[#2285] A suggestion for libraries such as base64.rb — Dave Thomas <dave@...>
Some of the older libraries simply insert stuff into the top-level
[#2305] Time#usec round trip problem — Minero Aoki <aamine@...>
Hi,
[#2306] YAML.dump("a".."z") — Minero Aoki <aamine@...>
Hi,
Re: Best way to install ri documentation -- please check this
On Tue, 6 Jan 2004 00:47:41 +0900
Dave Thomas <dave@pragprog.com> wrote:
> > Is DESTDIR effective to --ri-system?
>
> I have no idea: it uses rbconfig:
>
> base = File.join(Config::CONFIG['datadir'], "ri", version)
> SYSDIR = File.join(base, "system")
> SITEDIR = File.join(base, "site")
>
> If this isn't sufficient, what do I need to do to change it?
The first problem with using DESTDIR I've run into is that ruby may not
be installed in its final place yet when rdoc is run, leaving you
with this:
/usr/local/bin/ruby ./bin/rdoc --all --ri-system .
make: /usr/local/bin/ruby: Command not found
Trying to use miniruby would give you this:
./miniruby ./bin/rdoc --all --ri-system .
./bin/rdoc:59:in `require': No such file to load -- rdoc/rdoc (LoadError)
from ./bin/rdoc:59
This gets you further:
/miniruby -Ilib ./bin/rdoc --all --ri-system .
but then eventuall fails with this:
Generating RI...
./lib/yaml.rb:17:in `require': No such file to load -- yaml/parser (LoadError)
from ./lib/yaml.rb:17
from ./lib/rdoc/ri/ri_descriptions.rb:1:in `require'
from ./lib/rdoc/ri/ri_descriptions.rb:1
from ./lib/rdoc/ri/ri_reader.rb:1:in `require'
from ./lib/rdoc/ri/ri_reader.rb:1
from ./lib/rdoc/generators/ri_generator.rb:46:in `require'
from ./lib/rdoc/generators/ri_generator.rb:46
from ./lib/rdoc/rdoc.rb:243:in `require'
from ./lib/rdoc/rdoc.rb:243:in `document'
from ./bin/rdoc:63
While I'm fine with building the docs here, would it be worthwhile to simply
bundle the already built docs with the source dist? Then, they could be
installed in the right place when DESTDIR is supplied, and there's no need to
worry about ruby being in it's final installation location.
Jim