Amanda Waite wrote: > > Ruby and RubyGems have been integrated for a while now. If I was > integrating another package into SFW and wanted to use the gem command > to install some Ruby extensions during the build of that package, would > there be a preferred way to do it? Should I add the gem command to the > usr/src/Makefile.master as a build tool? What about versioning? This is > likely to be version sensitive, should I rely on the SFW requirement to > build on no older than 2 revs from the current build? Or should I do > version checking in the build scripts?
Ideally you really should use the command from the proto area (so you'd also need a dependency to guarantee it is built first and available before being used) to avoid dependencies on the build machine installation. If that's not at all possible then the alternative is to use the command on the system, which given the n-2 guideline should be there. You'd have to announce a flag day since introducing such a dependency means it won't be possible to build on a machine older than x. (But in this case gem has been around so long already, it's not much of a burden.) > BTW: I'm aware of the issues with packaging Gems that we've discussed at > length on this alias. In fact it's actually the main reason why I'm > doing this work. I know you're just exploring ideas at the moment but I encourage you to bring the discussion here as soon as you have some thoughts about it and certainly before you spend any significant time in implementation! -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
