Prashant Srinivasan wrote:
>
> Here it is - http://wikis.sun.com/display/WebStack/RoR_ARC_Case

> Including Ruby with Solaris - ARC Draft
> 
> Prashant Srinivasan <Prashant.Srinivasan at Sun.COM>
> 08 October 2007
> 
>         This project delivers Ruby into Solaris.
>         Ruby, the scripting language[1], and Rails, the associated web

But it doesn't deliver Rails, right? Just the ability to get it.

>         2.1.    Key objects.

I suggesting merging content of 2.1 and 2.3. It's more maintenance
(and review) work if layout is described in several places instead of
just one.

>         /usr/ruby/1.8/bin/testrb
>         /usr/ruby/rubygems/bin/gem

So unlike ruby, rubygems is not versioned?  Always backward compatible?

How tight is the relationship between ruby and rubygems?
Does it need a separate rubygems/bin (which I need to add separately to path)?

>         The compatibility expectations for Ruby are as follows:

Interesting... thanks for including, it's always useful.


>         2.4.    Packaging and Delivery
> 
>         The current proposal allows for the inclusion and coexistence
>         of multiple versions of Ruby by keeping each installation under
>         a version-specific subdirectory.  The package, SUNWruby,

You'll need a usr package (end in 'u') for the /usr content and a root
package (end in 'r') for the things outside /usr (see some of the
existing packages for examples).

Since the ruby dirs are versions, I think you need versioned pkg names
as well.


>         3.1.    Included Ruby Extensions.

Are the extensions ./configure-time options which get compiled in?

It seems now this case doesn't include any gems to make things more
consistent?  I suggest adding a paragraph explaining that approach.


>         A symbolic link will be created from the standard Solaris man page
>         location(/usr/share/man/man1/ruby.1) to
>         /usr/ruby/[<version>.<subversion>.<minor-subversion>]/man1/ruby.1.

It should include stability info (the Uncommitted) as well as a note
about obtaining sources on opensolaris.org.  I've seen some components
add the info to the manpage, others have a summary manpage which
describes the component along with Solaris-specific info and pointers
to the individual manpages in /usr/foo/man/*. Look for examples in the
sfw sources with names *.sunman

>         6.2.    Imported Interfaces.
> 
>         NAME                            STABILITY               NOTES
> 
>         Curses [CRT screen handling]    Stable

Where is the curses it's linking to? There should be an ARC case.

>         Readline[functions to edit command lines](statically linked into the 
> Ru
> by executable)  External
>         PSARC 2007/188

2007/188 hasn't delivered yet, so I assume you're just getting it from
elsewhere and compiling it in statically, as noted?


>         6.3.    Exported Interfaces.
>           There are no advertised programmatic interfaces.

ruby is a language ;-)
Tons of programmatic interfaces there.
(i.e. the language itself, bundled APIs etc)

Presumably it's all Uncommitted, but call it out.

>           [7]     
> http://wikis.sun.com/display/WebStack/Directory_and_File_Layo
> ut

It seems to deliver much documentation under /var/rubygems/repository/doc/
Is this "/var" content? It changes during runtime and/or users modify it?
If it's just documentation why isn't it under /usr?


-- 
Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems

Reply via email to