--m51xatjYGsM+13rf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 22:25 Mon 23 Jan, Austin Ziegler wrote:
> On 23/01/06, Kirill A. Shutemov <k.shutemov / sam-solutions.net> wrote:
> > Build and install system changes:
> >
> > FHS:
> >
> > - pure-ruby files install separete from ruby extentions(binary).
> >   /usr/share/ruby/X.Y for *.rb
> >   /usr/lib/ruby/X.Y for *.so
> >
> > - ruby headers install to /usr/include/ruby/X.Y/
> >
> > Non-FHS:
> >
> > - vendor-specific ruby-modules dirs. It's useful for a distribution. We
> >   have three type of ruby-modules:
> >   1. stdlib
> >   2. vendor-specific(a ruby modules prepared for a distribution)
> >   3. user's modules which installed by hand
> 
> I don't think that this is a useful modification. If a particular
> repackager wants to use this, feel free, but I think that the current
> installation layout is more than sufficient and is overall better for
> its cleanliness.o

I don't think that scrap-heap of header, rb and binary files is very
cleanliness.

> If you want something more applicable that makes it useful to
> repackagers and people who couldn't care less about the Linux-specific
> FHS (e.g., anyone using Windows or a Unix other than Linux), make it
> something which can be applied with a specific configure option (e.g.,
> --enable-fhs-install). Even when I use Linux, if I'm installing from
> source, I don't necessarily want to follow FHS, and your patch *only*
> allows for FHS installs on Linux.
> 
> Also, your change to --with-sitedir is not appropriate, since binary
> extensions can end up there.
> 

I can add code to configure.in code to allow user specify rubyincludedir, 
archdir, rubylibdir, sitelibdir, sitearchdir. Is it what you want?

-- 
Kirill A. Shutemov				Belarus, Minsk
E-mail:	k.shutemov (AT) sam-solutions.net
JID: kas (AT) altlinux.org
ICQ: 152302675

The only "ism" Hollywood believes in is plagiarism.
		-- Dorothy Parker

--m51xatjYGsM+13rf
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD1ONjbWYnhzC5v6oRAvNuAJwL7HlKmUdn0IqdWVoDnWhcEtJ7TgCgkB9f
ioo0NmtS+qKluVEEWZ6TAIw	Am
-----END PGP SIGNATURE-----

--m51xatjYGsM+13rf--