Prashant Srinivasan wrote: > > Hello, > > Can interested folk please review the ARC case for Rails that Amanda > and I put together? > > http://wikis.sun.com/display/WebStack/Rails_Draft_ARC_Case
> All other objects will be contained within the > /var/ruby/1.8/gem_home hierarchy, specifically, in the > below directories: > > /var/ruby/1.8/gem_home/ > cache > doc > gems > specifications This isn't right.. That's exactly where they end up if one runs 'gem install rails' today. So package updates and gem install runs will continually stomp on each other in various ways depending on ordering. System auditing will also show package-delivered files are corrupted. (Also if some binaries like 'rails' are elsewhere, in what interesting ways can things blow up when they're out of sync with what used to be there before gem/pkg overwrote whatever pkg/gem previously installed?) If Ruby is to support both package-delivered and gem-delivered content, there needs to be a design that specifies how they can coexist. This case needs to consider and address that issue. > Additional Ruby Libraries required to support three of the most > popular databases for Rails applications are: > > mysql > postgres Does this create any dependencies to MySQL and/or Postgres packages? > sqllite Does this depend on the SQLite package and if so, is it on the 3.x that's being worked on currently? (If yes, this case needs to document a dependency on that case.) > The Ruby application components required by Rails and which must > be integrated at the same time as Rails are: > > rake I see in debian rake is delivered separately. Is it desirable to require installation of rails for someone who only needs rake (if that's a reasonably common use case)? -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
