Prashant Srinivasan wrote: > > So, in order to make using Ruby as easy as possible to folks with > different preferences, we're considering packaging two versions of > rbconfig.rb, one tailor made for gcc, and the other for Sun Studio. > > rbconfig.rb will be a symlink, and point to the gcc configuration. > This is to make it seamless for a user of native Ruby gems like MySQL, > Postgres etc., to get started without needing to learn about compiler > locations/flags and the nitty-gritty.
Sounds like a reasonable, if unfortunate, compromise to me. You'd definitely want it to work out of the box and while gcc is always available (on both Indiana & Nevada builds), many sites don't have Studio installed. > The Studio configuration is for users who tend to have Sun Studio > already installed on their systems - they get to use this by manually > changing the rbconfig.rb symlink to point to rbconfig.rb.sun_studio Hm, you'd have to make the link editable (in the pkg) but I don't remember if that's possible. (If not you could deliver the gcc rbconfig.rb in place, marked editable and then the studio-rbconfig.rb as an example and document that it can be copied over if desired.) -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
