Jyri Virkki wrote: > 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. >
Fair enough, we can copy the gem command from the proto area, patch it so that it's pathing is correct (it won't run as is from the proto area because it thinks it's in /usr) and then install the Gems using the copied and patched file. The changes are such that there really should be no problem from updates to the RubyGems. The way we are doing this we can pretty much template the whole process for any gems we package. > 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! > > Will do and thanks for the advice. Amanda
