kinda newbie question

Kim Holburn kim.holburn at
Tue Jan 15 14:55:45 EST 2002

At 2:17 PM +1100 02/1/15, Damien Elmes wrote:
>Sam Couter <sam at> writes:
>> mn_x at <mn_x at> wrote:
>> > yes, it gives me: make: *** No rule to make target `uninstall'.  Stop.
>> So now you have to do it the Windows way: Search through your filesystem
>> in the areas that the software may have installed itself (probably
>> /usr/local) and delete each file that the package installed manually.
>> If you still have the source package configured (and its Makefiles are
>> set up decently), you could probably do something like "make
>> prefix=/tmp/foo" and see what files go into /tmp/foo. Look for those
>> same files in /usr/local.
>> Using a package management tool like dpkg or apt on Debian or rpm on
> > RedHat will solve all of these problems for you.
>There's also programs which can wrap a 'make install' process and record where
>everything's going. But package management is much more sane. That's what
>/usr/local was invented for in the first place (source code installations which
>were easy to prune)

If someone else from redhat or debian has already compiled the code and created a package in just the way you need it then that would be the best option.  Otherwise you are on your own.

I like the package management systems but till recently there was no easy way for me to compile and create packages for me to use. 

Are you suggesting that we give up everything that doesn't come pre-compiled from a distributor? 

Or just live with a nice package management system with the occasional splatter of files from a diy release? 

Putting everything in /usr/local (shudder) or /opt is one option.  Of course you have to hope that everything really does go there.


Kim Holburn  Network Consultant  P/F: +61 2 61258620 M: +61 0417820641
Email: kim.holburn at - PGP Public Key on request

Life is complex - It has real and imaginary parts.
     Andrea Leistra (rec.arts.sf.written.Robert-jordan)

More information about the linux mailing list