Kai Hendry wrote:
>Yes, this is a little dumb on an unstable Debian system with rails, rake >active* installed. > > > [snip] >... > >Any comments? Does it overwrite the Debian install of Rails?? what what? > > Maybe, maybe not. I'm not sure where gems writes stuff, especially since you run it as a superuser. I don't think it would overwrite Debian installation, but then you never know. The only way to check is to run debsums on a given package and see what happens. debsums rails This is in the debian package debsums. To only report errors, just run debsums -s rails But you might have overwritten other files as well, so might want to run debsums on all packages, debums -s It may create some noise about 'no md5sums for foo', but you can ignore those. What I would do, if you need to use gems to install things, is to run a debian chroot and use gems there. That is, you only install ruby with apt-get and then use gems for everything else. Since that would be in a chroot, your Debian system would still be safe. For documentation on installing debian in a chroot visit the Debian documentation page, or more specifically, http://www.us.debian.org/doc/manuals/reference/ch-tips.en.html#s-chroot Hope this helps, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
