No need to CC me, I'm on the list.
See FAQ/1.3.
As to make, I guess you don't use make -n install. It doesn't actually
install, just shows you what's going to happen. That's one way. Another
I case of qmail, you see nothing: make setup check.
is to actually look at (and modify if necessary) the makefiles before you
even start.
In case of qmail, you look at hier.c.
Knowing where things are gonna go in advance is something I
learned a long time ago with earlier versions of innd.
Before you install an rpm, you do
rpm -qpl package.rpm
to see where things will go. Once the package is installed, you do
rpm -ql
to see all the files installed. Now, how can you check where your gcc
files are when 1 year later you would like to update it, or 2 mos
later when a user cannot find a header file for objective C?
How can you be certain that when you install a new package it will not
nuke some files from other packages? How about config files? You
back them up before every upgrade?
In any case, I know that one can take care of everything by hand---but
terribly errorprone, and repetitive.
Mate
