David Van Couvering wrote: > > To me, getting a Ruby webstack without Rails is like getting a car > without doors. It just doesn't make sense, even if it is easy to install.
Well, a bad analogy, since for [regular street] cars doors are required... Whereas Rails isn't anywhere near a requirement for using Ruby. Ruby is a general pupose language useful for countless things without Rails. Also keep in mind that if a Rails package is available it still needs to be installed. It's not significantly different having to type "pkg install SUNWruby18-rails" vs. having to type "gem install rails". (Some might argue the latter is easier because Ruby developers are already familiar with that approach.) In terms of keeping versions and dependencies in sync there are benefits to having a pre-packaged gems. On the other hand it means thinking through and testing the cohabitation of gem-installed vs. pkg-installed gems. It should all be solvable, some of the discussions happened already here, but the Ruby team decided there wasn't enough time for the initial integration to polish all the edges. The discussion should revive as the team picks up that work again, so stick around... > I know this is beyond the scope of this team, but it seems to me that we > should have some RBAC roles like 'Ruby Web Developer' and 'AMP Web > Developer' (or even a generic 'Developer' role) and give them all the > rights they need to be productive. Ideally, I should be prompted to > assign these roles as part of creating the initial user when I first > install Solaris. That's not beyond the scope of this community, it's been part of the discussions here. Packages need to be able to deliver user & access control related to itself. That'll include runtime user/groups for daemons, rights profiles and such. Unfortunately packages can't do that today (which is why mysql doesn't yet create its own user). There's an RFE for IPS to support it, add yourself to the interest list if you wish to follow its progress: http://defect.opensolaris.org/bz/show_bug.cgi?id=217 Apache already delivers (not directly, but through the consolidation, which is a hack that won't scale but as long as there's only a few components it's a workaround) rights profiles to delegate its administration and I believe MySQL team is planning on doing the same. There could also be umbrella profiles (such as "Web Stack Developer") that combine the component-level rights, for administrative convenience. -- Jyri J. Virkki - jyri.virkki at sun.com - Sun Microsystems
