On 10/20/07, Chad Woolley <[EMAIL PROTECTED]> wrote: > On 10/20/07, Rick DeNatale <[EMAIL PROTECTED]> wrote: > > Somehow they think that that violates the FHS, or at least the debian > > policy interpretation of it. > > Look at the very end of: > > http://pkg-ruby-extras.alioth.debian.org/rubygems.html > > I can't say that I understand it, but that's what the Debian ruby > > maintainers think.
Actually, I thought that Trans was pointing to GoboLinux, which has made this decision. They may reuse the .deb format which may be the source of the confusion. I'm not sure, as I haven't actually looked at what Debian or Ubuntu do (I always build from source on these platforms). > That document really needs to quote the exact sections of FHS that are > violated, and why they consider them to be violated by Rubygems. It's > too vague to just say that RubyGems violates FHS because it "follows > the "one directory per package and version" rule." The Debian view, as far as I can tell, is centred around the idea that you *shouldn't* have more than one version of a library installed at any one time. I'm not sure. There is a legitimate problem with RubyGems and normal Unix layout, if Ruby is installed in /usr/bin and /usr/lib instead of /usr/local/bin and /usr/local/lib, because there are native libraries that can be built into the target directory. /usr/bin is supposed to be able to be NFS mountable; /usr/local/bin is supposed to be specific to a particular machine. That's the ONLY legitimate argument, and it's something that RubyGems will have to deal with in the future. There have been suggestions to make it so that gems can be installed in more than one directory, but that also complicates loading. That way, if Ruby is installed in /usr the .rb files will go in /usr/lib/gems/1.8/... and the .so files would go in /usr/local/lib/gems/1.8/.... > "This hierarchy holds state information pertaining to an application > or the system. State information is data that programs modify while > they run, and that pertains to one specific host. Users must never > need to modify files in /var/lib to configure a package's operation." Yeah. Whoever chose /var/lib chose wrong. But GoboLinux doesn't follow FHS, if that's the item in question. (GoboLinux is approaching it from a Mac-like approach. Unfortunately it doesn't quite work as well as that, and even the Mac still uses /usr and /usr/local and /opt and /opt/local...) -austin -- Austin Ziegler * [EMAIL PROTECTED] * http://www.halostatue.ca/ * [EMAIL PROTECTED] * http://www.halostatue.ca/feed/ * [EMAIL PROTECTED] _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
