On Sun, Apr 14, 2002 at 05:32:38PM -0700, Bart Schaefer wrote:
| On Sun, 14 Apr 2002, dman wrote:
| 
| > $(PREFIX) should normally be '' (or '/' if paths are properly
| > normalized after expansion).
| 
| You're thinking of GNU autoconf.

That's where most of my experience lies, and it seems nicely
consistent that way regardless of whether I'm the admin (on cygwin) or
a plain old user (solaris at school).  I don't actually use autoconf
on my home system because debian packages everything for me :-).

| SA uses Perl's ExtUtils::MakeMaker.  
| MakeMaker does not define $(PREFIX) that way.  MakeMaker defines $(PREFIX)
| as (by default) $Config{prefix} from Perl's Config module.  That is 
| normally /usr or /usr/local, not /, and Makefiles generated with MakeMaker
| install into $(PREFIX)/bin $(PREFIX)/share and so on.

That works great, until you get to config files.  /usr/etc just
doesn't cut it.  $(PREFIX)/../etc is fine, until a user tries to use
$HOME as $(PREFIX).  Maybe there should be some flag that can be set
to indicate whether or not this is a "system" install.  If it is a
"system" install, use $(PREFIX)/../etc, otherwise $(PREFIX)/etc.

A more consistent (yet also not terribly pretty) alternative is to
always use $(PREFIX)/../<realpath> for everything, and tell non-system
installs to set $(PREFIX) to $HOME/foo (where 'foo' is irrelevant
except for providing the extra indirection).

-D

-- 

I tell you the truth, everyone who sins is a slave to sin.  Now a slave
has no permanent place in the family, but a son belongs to it forever.
So if the Son sets you free, you will be free indeed.
        John 8:34-36


_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to