No. I put *my* code in SVN/CVS. The problem that the OP mentioned was
that *his* code was in C:\ruby while his installation was in
C:\Ruby182. When he tried to install 1.8.4, it *defaulted* to C:\ruby
(which is the *real* bad behaviour; it should have defaulted to
1.8.4). Then he did an uninstall and it deleted everything -- without
prompting -- in C:\ruby.
Third-party gems ... if they're that important, I'll make sure I have
a list to bring my install back up to speed, but otherwise I just
reinstall them as I need them.
-austin
···
On 5/31/06, James Britt <james_b@neurogami.com> wrote:
Austin Ziegler wrote:
> On 5/31/06, James Britt <james_b@neurogami.com> wrote:
>> 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.
> I put them in the ruby application directory ... after I have them in
> SVN or CVS. 
You put your third-party gems into SVN/CVS? After running 'gem install
<gem_name>' ?
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca
I think C:\ruby is a reasonable default installation location. Adding
the version just makes it longer and ugly, IMO. Anyhow as of the
latest installer code, a user cannot install into an existing
directory, and the uninstall let's them know the whole installation
directory will be deleted.
If they have problems after that, it is just user error.
As others have discussed, I think it is smart to develop code outside
of the Ruby installation directory, keep it maintained in SVN or CVS,
and then have a rake task or other script install it into the Ruby lib
directory.
Ryan
···
On 5/31/06, Austin Ziegler <halostatue@gmail.com> wrote:
When he tried to install 1.8.4, it *defaulted* to C:\ruby
(which is the *real* bad behaviour; it should have defaulted to
1.8.4). Then he did an uninstall and it deleted everything -- without
prompting -- in C:\ruby.
Um. That's not what I meant to say. It defaulted to C:\ruby but should
have defaulted to C:
\ruby182 which is where he had previously installed Ruby.
Why can't a user install into an existing directory? Does this mean if
I have Ruby 1.8.2 installed in C:\Apps\Ruby and want to install Ruby
1.8.4 there on top of it, I have to remove or uninstall 1.8.2 *first*?
-austin
···
On 5/31/06, Ryan Leavengood <leavengood@gmail.com> wrote:
On 5/31/06, Austin Ziegler <halostatue@gmail.com> wrote:
> When he tried to install 1.8.4, it *defaulted* to C:\ruby
> (which is the *real* bad behaviour; it should have defaulted to
> 1.8.4). Then he did an uninstall and it deleted everything -- without
> prompting -- in C:\ruby.
I think C:\ruby is a reasonable default installation location. Adding
the version just makes it longer and ugly, IMO. Anyhow as of the
latest installer code, a user cannot install into an existing
directory, and the uninstall let's them know the whole installation
directory will be deleted.
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca
Yep. We have discussed this in other threads recently. For example see
this post of mine:
http://ruby-talk.org/cgi-bin/scat.rb/ruby/ruby-talk/194831
As well as others in that thread.
Ryan
···
On 5/31/06, Austin Ziegler <halostatue@gmail.com> wrote:
Um. That's not what I meant to say. It defaulted to C:\ruby but should
have defaulted to C:
\ruby182 which is where he had previously installed Ruby.
Why can't a user install into an existing directory? Does this mean if
I have Ruby 1.8.2 installed in C:\Apps\Ruby and want to install Ruby
1.8.4 there on top of it, I have to remove or uninstall 1.8.2 *first*?
Austin Ziegler wrote:
...
Why can't a user install into an existing directory? Does this mean if
I have Ruby 1.8.2 installed in C:\Apps\Ruby and want to install Ruby
1.8.4 there on top of it, I have to remove or uninstall 1.8.2 *first*?
Yes. And reinstall any code not included with the Ruby distro, such as gems and other 3rd-party libs, that have been installed into that directory path.
···
--
James Britt
http://www.ruby-doc.org - Ruby Help & Documentation
Ruby Code & Style - The Journal By & For Rubyists
http://www.rubystuff.com - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com - Playing with Better Toys
http://www.30secondrule.com - Building Better Tools
Hopefully, this will only be a 1.8.2 -> 1.8.4 oddity. It should *not*
be the case with compatible compiler versions.
-austin
···
On 5/31/06, Ryan Leavengood <leavengood@gmail.com> wrote:
On 5/31/06, Austin Ziegler <halostatue@gmail.com> wrote:
> Um. That's not what I meant to say. It defaulted to C:\ruby but should
> have defaulted to C:
> \ruby182 which is where he had previously installed Ruby.
> Why can't a user install into an existing directory? Does this mean if
> I have Ruby 1.8.2 installed in C:\Apps\Ruby and want to install Ruby
> 1.8.4 there on top of it, I have to remove or uninstall 1.8.2 *first*?
Yep. We have discussed this in other threads recently. For example see
this post of mine:
http://ruby-talk.org/cgi-bin/scat.rb/ruby/ruby-talk/194831
As well as others in that thread.
--
Austin Ziegler * halostatue@gmail.com
* Alternate: austin@halostatue.ca