On 11/ 7/12 11:37 AM, Drew Fisher wrote:
On 11/7/12 10:53 AM, April Chin wrote:
On 11/ 7/12 08:53 AM, Drew Fisher wrote:
The rubygems installer (gem) has options for specifying an install
directory and a binary directory. Ruby also has an environment
variable like PYTHONPATH for searching non-default directories for
modules so I think we could rig something in the makefiles to handle
this, but I wanted to check first. Is it worth going to these
lengths to get the unittests working? Is it possible that we
evaluate the inclusion of these Ruby modules in our Ruby package?
I'd rather see additional Ruby modules packaged separately, rather than
bundled into the ruby package.
What I meant was I think if we find these gems useful, we should
evaluate them each individually and add them to our ruby-18 (and
ruby-19) package so users could have a more complete utility.
The ruby-18 and ruby-19 packages have/will have close to 20,000+ files each.
Unless upstream bundles them into their ruby (as rake and rubygems are
in ruby 1.9.3),
I would prefer to see additional gems put in separate packages.
If we wanted to allow a user to easily install all the ruby-related pieces,
we could create a ruby meta-package that included ruby along with the
gem packages.
If you'd like, I can post a webrev (work in progress - not ready for
actual review) for you to glance at.
Sure, that's fine.
Is rake required only for testing Puppet or is it needed for building
also?
I will be bringing Ruby 1.9.3 into Solaris, which includes rake v0.8.7.
It looks like it's just for testing. I've been able to build Puppet
without rake.
Okay, sounds good--you don't need rake right away then.
thanks,
April
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
