------art_27636_20239174.1149093828643
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 5/31/06, James Britt <james_b / neurogami.com> wrote:
>
> Gregory Brown wrote:
> > On 5/29/06, Dave Burt <dave / burt.id.au> wrote:
> >
> >> Curt Hibbs wrote:
> >> > We'll add an alert dialog telling you that the entire dircetory will
> be
> >> > deleted and giving you the option to proceed or abort.
> >>
> >> FWIW, I far prefer this proposal to the alternative of _not_ deleting
> >> the whole installation directory.
> >
> >
> > 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
> > this.
>
> 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.
>
> This is the problem with nuking c:\ruby.  It is the parent for all gems
> and third-party libs.


Understandable, but there is also no guarantee that these gems/libs will be
compatible with the next Ruby release.

Curt

------art_27636_20239174.1149093828643--