>> (1) Use Solaris packaging exclusively(ie., gems not allowed). >> (2) Get Solaris and Rubygems to co-exist. >> (3) Use Rubygems exclusively. ie., don't bundle Rails. >> >> > I'm a supporter of option 3), I feel that we'll just tie ourselves in > knots if we do 2) and 1) is just not going to fly with anyone who's used > Rails before. > But having said that, an idea would be to have a Solaris package that's > built around Gem management, where the package installer uses the Gem > command to check for an existing installation of the Gems that the > packages bundle, then displays what's installed currently and offers the > user the choice to do nothing or to install the Gems. In that case the > Solaris package would just be a wrapper package (i.e. Rails Support) and > not actually package any files. The package itself could setup a local > (and temporary) Gem repository. > > It sounds complicated and probably impossible given the packaging > restrictions we have.
Yeah, this will need us to introduce scripting into the packages . . . and Indiana will not be able to use it. -ps
