On 10/20/07, Rick DeNatale <[EMAIL PROTECTED]> wrote: > > Again, I'm just trying to understand the debian policy on gems myself, > but I suspect that the problem comes from this section of the Debian > Policy Manual: > > http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 > > "9.1.2 Site-specific programs > > As mandated by the FHS, packages must not place any files in > /usr/local, either by putting them in the file system archive to be > unpacked by dpkg or by manipulating them in their maintainer scripts. > " > > As I understand it, Debian policy requires package installation to > keep its hands off the /usr/local tree. Stuff put in /usr/local by > the system administrator is supposed to be safe from being changed by > package installations/updates etc. > > I thnk that this makes sense, however what's being described is the > package which installs rubygems. The maintainer seems to be > interpreting this as forbidding gem when executed from placing things > under /usr/local, but I think that this is being too strict. In fact > just below the quoted passage the Debian Policy manual says: > > "However, the package may create empty directories below /usr/local so > that the system administrator knows where to place site-specific > files. These are not directories in /usr/local, but are children of > directories in /usr/local. These directories (/usr/local/*/dir/) > should be removed on package removal if they are empty. > > Note, that this applies only to directories below /usr/local, not in > /usr/local. Packages must not create sub-directories in the directory > /usr/local itself, except those listed in FHS, section 4.5. However, > you may create directories below them as you wish. You must not remove > any of the directories listed in 4.5, even if you created them. " > > So, the debian gem package could be configured to put the gems under > /usr/local/lib/ruby... and to create empty directories as needed when > installed. > > But I'm not a debian maintainer so I don't know if there are other > restrictions.
Me neither, but I just thank Gobo developers for the openness about where to put my gems. :-) Maybe I should boot that up and send the recipe back to the community. Gems are installed in /Files/RubyGems/gems (and the stubs are inside /Files/RubyGems/bin). Good weekend everybody. -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
