On Jul 25, 2007, at 15:18, Alexey Verkhovsky wrote: >>> 1. Get rid of sources.gem >> >> Maybe a hybrid approach? A sources .gem and a default fallback to >> gems.rubyforge.org if the sources gem isn't installed? >> There's some anti-foot-shooting code that's wrapped up in there too, >> and I don't want people to shoot themselves in the foot. > > Silently defaulting to gems.rubyforge.org is OK. Configuring gem > sources by installing a gem package, on the other hand, is a tad too > hard to explain to a regular sysadmin, in my experience. > > I'd rather manage package sources by editing /etc/rubygems > configuration file.
This sounds like an excellent way to do it. > Or, if we were to borrow a page from yum, by adding/deleting .repo > files in /etc/rubygems/sources.d/ directory, but this may be too > fancy. Yum does it this way so that a repository metadata can be a > standalone file. Too fancy for me. -- 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
