[GRASS5] [gordon.keith@marine.csiro.au: [GRASSLIST:1295] Grass 5b10 make clean]

[Eric G . Miller]

In case you all didn't see this....  Can I make the recommendation that
we remove all of the "rm" statements from Makefile.in that work on the
install directories?  If we want an uninstall routine, I think it needs
a list of all the installed files (and where they were installed), so
the process can be done safely.  "clean", "distclean" and "mostlyclean"
should only affect the build directory.

My 2¢

----- Forwarded message from Gordon Keith <gordon.keith at marine.csiro.au> -----

Date: Tue, 19 Dec 2000 11:59:08 +1100
From: Gordon Keith <gordon.keith at marine.csiro.au>
Subject: [GRASSLIST:1295] Grass 5b10 make clean
To: grasslist at baylor.edu
Organization: CSIRO Marine Research

I am trying to install Grass 5 beta 10 on an solaris intel box.

I was unable to install from the binaries so I downloaded the source and 
tried to build it.

I followed the instructions and did a "./configure" and "make install". 
The error.log contained a lot of entries so I decided to "make clean" 
and "make all" to try to track down the error messages.

Since make install requires root access I was doing this as root.

Can you image my horror when "make clean" flashed up:

/bin/sh -c "rm -rf /usr/local/bin/   2>/dev/null ; true"

and proceeded to do the same for a few other important directories such as:
/usr/local/lib, /usr/local/include, /usr/local/man, etc.

Can I suggest (in _*extrememly strong*_ terms) that wiping out the 
entire development environment (gcc, make etc) is NOT what most people 
mean by make clean.

Please make it a little safer for newbies to play with grass.

Regards
Gordon



----- End forwarded message -----

-- 
Eric G. Miller <egm2 at jps.net>

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'