On Oct 12, 2007, at 10:23 , Prashant Srinivasan wrote: > Eric Hodel wrote: >> On Oct 11, 2007, at 23:32 , Prashant Srinivasan wrote: >>> I'm hoping to get rubygems bundled with the OpenSolaris OS, and >>> have >>> some questions about rubygems compatibility/stability etc., which I >>> couldn't find direct answers to. Any thoughts/pointers are most >>> appreciated. >> >> Cool. I hope it will be possible for people to upgrade RubyGems upon >> new RubyGems releases. > > Yes, that will be possible( and encouraged, since I'm the only > volunteer at this time, and I'll probably be able to update the > Solaris > packages only occasionally). > > I'm proposing that OpenSolaris bundle the latest stable snapshot > as it > is. So the upgradeability will not be affected. The Gem repository > location will be in /var/ruby. This is is to provide users of sparse > root zones with rubygems, while giving them the ability to modify > their > local copy of the gem repository. (in a sparse root zone, /usr is > read-only, since it's loopback mounted across different zones on the > system. But /var is a file system that is local to each zone, and > it's > contents are replicated across zones).
Ok. RubyGems has a feature that may be helpful. Multiple gem repositories may be used if they are specified in GEM_PATH. >>> -> Are rubygems versions compatible with previous releases(or >>> previous minor releases . . . or previous point releases)? >> >> We've made a best effort to keep RubyGems backwards and forwards >> compatible across all releases, but sometimes we've made mistakes. > > That makes it easy to package. > >> RubyGems versioning scheme seems nonexistent, so I don't know what >> the distinction has been between minor and teeny releases. >> >> Sometimes features become deprecated over the course of at least two >> releases before being removed. > > Just to verify, 2 releases here means two minor releases? For the past several releases there has been no distinction between the minor and major releases in version numbers, so for now, deprecated features will exist for at least six months after being marked for deprecation. This should be at least two "minor" releases. I would like to move RubyGems to 1.0 and give it a sane versioning scheme. After that, two minor releases will be the minimum. Hopefully this will happen by year-end. -- Poor workers blame their tools. Good workers build better tools. The best workers get their tools to do the work for them. -- Syndicate Wars _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
