Re: Why no docs for ruby ?

On 10/11/2012 05:22 PM, Vincent Batts wrote:
> On Thu, Oct 11, 2012 at 6:17 AM, Timothy Madden <[email protected]> wrote:
>> On 10/11/2012 04:50 AM, Vincent Batts wrote:
>>>
>>> This is true. I just put a simple build up
>>> http://slackware.com/~vbatts/ruby/ that just builds an addendum package
>>> called 'ruby-doc'
>>> I lobbied for this SlackBuild to be in /extra/, but we can't all get
>>> what we want ;-)
>>
>> This is just so sad ... ! :(
>>
>> As I said, it seems unfair to me some languages have a proper package,
>> others have only a trimmed package without documentation.
>
> I am two ways about this, because I too wholly want the package "ruby"
> to include all the pieces (including the documentation).
> But one of the things that I like very much about python's
> documentation strategy is that the documentation is not separate from
> the code. Even within the language, you can query an object for it's
> __doc__, so the pydoc utility needs only to lookup the path of the
> library references and read the documentation straight from the
> source, or even render a webserver that actively does the same.
> Unfortunately, this process is duplicated in ruby. Rdoc parses and
> renders new files, further one for `ri`, and another that is an html
> structure.

First, what does it mean "to save some space" from the Slackware 
distribution ?

I see the DVD for 14.0 is at 2.3 Gb, meaning it is far from full. The 
CDs, however, are about 660-670 Mb each, which I guess means they are 
all full indeed...

Is there a way to make ruby-doc available to slackpkg only ? Is there no 
packages "repository" concept for slackware ? Are the extra/ packages 
included in the size of the distribution ?

About ruby documentation system, I believe python has offline 
documentation that is not generated on-the-fly with pydoc, but it is 
really there in disk files. Anyway, it is my belief that the packaging 
or distribution of the product should not mandate how the product should 
work internally, so whatever documentation system they choose, it is 
their choice.

Thank you,
Timothy Madden