From: Tim Ferrell Date: 2008-02-29T22:56:34+09:00 Subject: Re: ruby tk -- how do you get it working? 7stud -- wrote: > > So some developer assumed that /usr/local would be empty except for > their install? Heck why didn't they just say, "Our install is easy to > uninstall: delete your hard drive and it's gone. What could be > simpler?" Well, that would definitely qualify as an easy uninstall ;-0 Of course it wouldn't leave you with a usable system but that is another issue... hehe > Their app didn't create a folder--it installed files all over the place Actually, it may *have* created that /usr/local hierarchy unless you have installed other stuff there yourself... Did you? If not then it should be safe to just delete the stuff under /usr/local, although writing a script to delete from the installer bom would be the best choice, in my opinion... Just FYI, you can extract a list of files from a .bom file with the following command: lsbom -s > I should be able to manage a script like that on my own. Will deleting > anything under usr/local affect the operation of the pre-installed ruby? > After I delete all the files will the pre-installed ruby automatically > work, or is there some link somewhere that I have to change? No - all of the bundled stuff is under /usr/bin, etc (/usr/local is typically reserved for user-installed stuff) so it won't affect the apple-supplied ruby... > >> Anyway, going forward, I'd suggest you use MacPorts to install and >> maintain a "non-Apple" version of Ruby - the Ruby port maintainer is >> great about keeping it up to date with the latest patch level and you >> can choose between version with and without tk... There are even a few >> gui tools to manage installed ports if you prefer that kind of thing... >> > > Ok, thanks. One thing to note: if you plan to upgrade to Leopard then it wouldn't really be needed, as the latest versions of ruby (1.8.6-p111) and rubygems (1.0.1) are included in the 10.5.2 update and, as long as you install the developer tools, then Tk will work out of the box... Cheers, Tim -- Posted via http://www.ruby-forum.com/.