Re: About the Ruby packages split: a concrete proposal
- To: Debian Ruby list <firstname.lastname@example.org>
- Subject: Re: About the Ruby packages split: a concrete proposal
- From: akira yamada <email@example.com>
- Date: Thu, 03 Mar 2005 00:41:13 +0900
- Message-id: <4225DE99.firstname.lastname@example.org>
- In-reply-to: <20050209233931.GA9396@power.luon.net>
- References: <20050127130626.GA24861@chistera.yi.org> <420A2FEA.email@example.com> <20050209233931.GA9396@power.luon.net>
I prepared restructured version of ruby1.8.
It is available on http://people.debian.org/~akira/ruby1.8/
I think that restructuring ruby1.8 can separate into two steps.
1st step is to merge some packages.
2nd step is to introduce new meta packages.
The new ruby1.8 is for the 1st step.
(NOTE: 1.8.2-2+1 may be canceled for some reasons.)
Paul van Tilburg wrote:
> What criteria did you use for this. We tried to leave out libraries
> with depends on other libs as well but came to the conclusion that
> since libgdbm and libopenssl are either base or standard, everyone will
> have those installed almost always as well.
I think that ruby1.8 + libruby1.8 should depend on minimum packages.
> AFAIK 99% the people I speak think ruby installs the interpreter and the
> assumed base libraries (seeing apt-cache show python2.3 (where most of
> the library doesn't seem to be split of at all) and apt-cache show perl).
For Debian environment, "the interpreter and
the assumed base libraries" is new ruby1.8 + new libruby1.8.
New libruby1.8 includes "base libraries on Debian environment".
All of extension libraries are optional on upstream release.
Because these libraries can be omitted by configure options or
akira yamada <URL:http://arika.org>