On 5/31/06, James B. email@example.com wrote:
I think that might get mucky, since the directory structure might
change from release to release and things like that.
My employer always sticks ruby scripts I write for him in with the
ruby distribution. This drives me bonkers, I have no idea why he does
Where do people put their custom libs, the code they want available to
all their Ruby apps? I tend to put them in site_ruby.
I was under the impression that they ‘belonged’ site_ruby.
This is the problem with nuking c:\ruby. It is the parent for all gems
and third-party libs.
I’ve recently solved this issue (for my own code) by doing all of my
own dev in one main directory, with subdirectories for each
project/library, then using a Rake task to ‘install’ the code where it
This gives me one main directory that I controll with all of my work.
The finished product can end up in the site_ruby directory, or some
client’s local web directory, etc. I always have my main source with
notes seperate, covered by subversion, and on a scheduled backup (yes,
I’m paranoid. I’ve learned to be over the years).