From: "Zachary P. Landau" Date: 2003-10-02T04:40:27+09:00 Subject: Re: [RCR] Include CONFIG::Config['rubydocdir'] in rbconfig.rb --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > |Summary: if Ruby had a standard documentation directory, then > |installers could install documentation there. A typical Ruby > |installation does contain documentation in a sensible place, but this > |location is not retrievable through the normal Config['xyz'] > |mechanism. >=20 > Currently it does not have one. Where do you think it should be, if > Ruby should have a standard documentation directory. And how far > should it cover? Libraries? Applications? The documentation dir should probably only handle libraries. With applications, it shouldn't matter what language they are written in, so the documentation should go in the same place as any other program documentation. You wouldn't have /usr/share/doc/c/gawk/README or something like that. Libraries are used when people are writing something in the same programming language, so it should make sense to put those in something like /usr/share/doc/ruby/ruby-gtk2/README. So maybe we want Config['libdocs'] or something that shows it is for ruby libraries and applications.=20 --=20 Zachary P. Landau GPG: gpg --recv-key 0x24E5AD99 | http://kapheine.hypa.net/kapheine.asc --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/ey2XCwWyMCTlrZkRAsJfAJwJpjCi12VmdXWorVifIhQYqQZFEACeKK4r Nbzexo0+KesMTcCfVCfITI8= =czgX -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+--