Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

How to uninstall MacGIMP [out of date hint!] UNIX
2005 Update: MacGIMP can be uninstalled by dragging to the trash. The original hint remains as published below...

This is my solution to the (serious) issue of uninstalling the over 360 files installed by MacGIMP.
I have looked everywhere and cannot find a decent solution to the problem... many folks seem to be asking how to do this so here goes.
First I made a list of the files I wanted to remove:
  1. open Terminal and navigate to your hard drive folder...

  2. create an empty text document. I used the following to do this:
    touch myfilename.txt
    Leave the document there (call it whatever you like, I used trashGimp.txt).

  3. type in the following:
    sudo find / -group 17025 -iname "*gimp*" | sort > trashGimp.txt
All that this will do is give you a sorted list of every file, directory and app that is assigned to group 17025 (which SEEMS to be the same number in all cases of MacGIMP installation... check and make sure) AND has some form of the word "gimp" in it. This is just so you can see what you are going to eliminate and where it came from
Now... how to remove it all... the easiest way would probably be to issue the following:
sudo find / -group 17025 -iname "*gimp*" -exec rm {} \;
This will only delete the files, not the actual directories that are included in this find. For that you need to substitute rmdir for rm. Note that directories that still contain items cannot be removed with rmdir.

Why do I want to remove MacGIMP? For one, I want to install fink and the fink ReadMe says not to use the installer if MacGIMP is present. Also, I am a professional Photoshop user and GIMP, while nice for people who don't want to shell out big bucks for a graphics app, cannot hold a candle to Adobe's product.

Any unix experts out there can undoubtedly improve on the methods listed here. I am just trying to get the issue out in the open as there are frustrated folks all over various discussion boards trying to figure out how to get rid of MacGIMP.

[Dec 22, 2003 Update: The information above regarding MacGIMP and the fink project is out of date -- MacGIMP and fink can happily co-exist. According to the MacGIMP folks, an upcoming release of MacGIMP will contain an uninstaller that makes removal of MacGIMP a simple process. I'm leaving this article online as a reference for those with older versions of the software; the reasons for removing it may differ person by person, but this hint and its comments contain useful information for those who wish to uninstall MacGIMP.]

    •    
  • Currently 1.00 / 5
  You rated: 1 / 5 (3 votes cast)
 
[10,018 views]  

How to uninstall MacGIMP [out of date hint!] | 17 comments | Create New Account
Click here to return to the 'How to uninstall MacGIMP [out of date hint!]' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
How to uninstall MacGIMP
Authored by: reh on Nov 25, '03 11:18:54AM

Step number 2 is unnecessary.

---
12" iBook ~ 800MHz G3 ~ 640MB ~ 30GB ~ Combo drive ~ Panther



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: LC on Nov 25, '03 11:24:43AM

stdout redirect creates the file



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: osxpounder on Nov 25, '03 05:25:00PM

Thanks, LC and reh, for pointing this out. What might seem "duh!" obvious to experienced Unix/Linux users turns out to be totally unknown to many of us Mac [and former Windows] users. I appreciate it.

---
--
osxpounder



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: elmimmo on Nov 26, '03 03:17:39AM
Actually,
> trashGimp.txt
works pretty much the same in Windows's prompt (and oldy MS-DOS).

[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: colmc on Nov 25, '03 11:39:58AM
There's no need to use rmdir. Simply use
rm -rf
to remove any file or directory including the files it contains. In your example:

sudo find / -group 17025 -iname "*gimp*" -print -exec rm -rf {} \;


[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: kevinh456 on Nov 25, '03 11:40:00AM

rm -R will recursively remove directories and files. You might want to be careful how you use this however.

---
Weeeeeee :-)



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: ChaChi on Nov 25, '03 12:10:15PM
Try this:

1.) Double click the "MacGimp" installer package
2.) Click "Continue"
3.) Select "Show Files" from the "File" menu
4.) Click "Save...", give the file a name and save it
5.) Quit the installer

This will give you a complete listing of the files that "MacGimp" installs on your system.

On my system the files installed by "MacGimp" got installed in an invisible directory named "/opt" at the root level of my Hard Drive. The only other files I could see that "MacGimp" installed were these two:
/usr/X11R6/lib/libjpeg.9.dylib
/usr/X11R6/lib/libjpeg.dylib

I just issued the following command in the "Terminal" to completely erase all of the files that "MacGimp" installed?

sudo rm -rf /opt /usr/X11R6/lib/libjpeg.9.dylib /usr/X11R6/lib/libjpeg.dylib

Not sure if it's the same for everyone though.

[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: hopthrisC on Nov 25, '03 01:27:38PM
I can't test it, but I very much suspect

lsbom /Library/Receipts/MacGimp.pkg/Contents/Archive.bom

(or something very similar), followed by a view sed lines to have the same effect.

[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: reiggin on Nov 25, '03 12:44:22PM

Interesting to see how other ppl approach the problem differently. Also interesting to see how a hint from someone calling himself "Cunning Linguist" was not up to par when compared to other solutions.



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: osxpounder on Nov 25, '03 05:31:05PM

I disagree; "Cunning Linguist" was kind enough to offer some help, and plenty of us are grateful. I don't know what you're getting at with the comment about the username.

---
--
osxpounder



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: reiggin on Nov 25, '03 08:06:59PM

I was joking/laughing when I made the comment. No ill-will meant towards the initial hinter. But I still do think it's interesting to read about the different ways to do the same thing. Versatility is nice amongst the community, and it's especially nice to see so many minds come together to deduce the best approach to solving the problem.



[ Reply to This | # ]
How to uninstall MacGIMP
Authored by: Crimson Napkin on Mar 05, '04 01:14:14PM

You are criticizing a tip that works just fine? Why?

The first two replies recommend the same change. A change that eliminates 1 step from the process. Great but not that big a deal.

The third reply says to use the -r flag. This works but could be risky for relative unix newbies to use. Yes it does save a step, no it doesn't alter the final outcome of the tip.

The fifth reply takes 6 or so steps to accomplish what my tip does in 2. He also seems to miss some MacGIMP files.

Then you toss out "not up to par when compared to other solutions". As the points above prove, your comment shows that you apparently didn't compare them.

I do not understand people like you. I offer a tip to help out... a tip that I could not find anywhere on the web... a tip that works and is safe for those new to unix to use... and you poop on it.

My suggestion for you and your ilk, be nice... not mean.

-Cunning Linguist

p.s. the name refers to skill at linguistics... what this has to do with skill at writing unix tips for OSXHints is beyond me.

---
macosxhints.com is one reason PC users should switch to a Mac.

[ Reply to This | # ]

How to uninstall MacGIMP
Authored by: rajd1 on Nov 25, '03 07:07:20PM

If your purpose is not to remove MacGimp, but to install fink, take a look at the fink upgrade page for advice and tips...

http://fink.sourceforge.net/download/upgrade.php

-Rob



[ Reply to This | # ]
Suggestion
Authored by: nyarlathotep on Nov 25, '03 09:21:16PM

As a general rule: Always use fink packages and avoid these funky packaging things like MacGIMP and the i-installer. Most apple software and good party software uses the Macs built in ppackage tracking system, which while it appears vastly inferior to fink's dpkg, does allows basic package managment operations.. and can help you resolve conflicts. Fink has a seperate (vastely superior) package managment system AND it avoids the main Mac OS X tree, but other third party installers, like the i-installer, will use their own package mangment system (or no package mangment system) AND tehy install into the /usr tree. This is just plain stupid and assking for trouble. Even if your third party installer knows lots about Macs, a single Apple automatic update could overwrite one of its files and send all sorts of things crashing down. Just say no. If these people were at all sane they would be using fink like everything else.



[ Reply to This | # ]
Suggestion
Authored by: Spades on Nov 26, '03 11:36:06AM
It's ok to use /usr/local. Apple should not be touching it. From the Filesystem Hierarchy Standard:
The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated.
In fact, my own suggestion is to avoid fink because it "avoids" the main OS X tree. As you can see, the whole reason /usr/local exists is for things like fink, and i-Installer. It's difficult for applications outside of fink to make use of fink libraries and applications because it is outside of the standard tree. If fink installed in /usr/local instead, a bin/init.csh script would be unnecesary.

[ Reply to This | # ]
Suggestion
Authored by: nyarlathotep on Jan 09, '04 01:12:04PM

Any given install tree needs a package management system. The /usr tree should bee managed by Apple's managment system, the /sw tree should be managed by dpkg, and /usr/local usually needs to be managed by hand.. a big pain in the arse.

Besides nobody has trouble using fink if you configure it properly, like by actuallly running its initscripts and being careful about use of enviroment variables.

I find that I'm better off with almost all fink stuff, though I have a /sw/local/bin directory which is the very first thing in my path and occasinally I need to place a symlink there wheen some program in /usr/local/bin or /usr/bin needs to run before a program in /sw/bin.. a very rare occurance indeed.



[ Reply to This | # ]
Suggestion
Authored by: Jim Hu on Nov 26, '03 12:43:37PM

I agree with Spades - fink would be fine if everything was released for fink - but it isn't, and lots of things that work in OSX work their way into fink slowly.

This means that sometimes, despite editing default paths and so on, things that you want to install - with CPAN, for example - just don't work with other things you installed with fink, unless you go in and edit config files all the time.

I thought fink was great at first, but now that I've learned how to install stuff into /usr/local CPAN works much better, and CPAN seems to update much more frequently than fink.



[ Reply to This | # ]