Duncan: Thanks for the comments.
> > I think it is perfectly acceptible to let the local admin decide where > he/she wants to put files. Why restrict, especially when the performance > gain/loss is so incredibly insignificant. > I agree that it is acceptable to allow the admin to choose, but the current install doesn't allow that. It doesn't even recognine the default paths from your local perl installation. We're stuck with the hard coded paths in the perl files, and are forced to make symlinks all over the file system. > Furthermore, this will break previously working systems on upgrade. For > what reason? None. > Well, we could keep the old path in there for historically purposes which would allow older upgrades to continue to work while giving those willing and option to use a cleaner structure. > > If you delete one path, delete /etc/mail/spamassassin. I don't know what > distribution has /etc/mail and what software supports this, but Debian > certainly does not. (Wouldn't it be stupid to have an /etc/mail with just > spamassassin stuff in it?) > Solaris, Redhat, and I think Mandrake to name a few. It's the standard *defualt* installation directory used by Sendmail as well. > If what you are saying is that you want all files to be in one directory, > I'm going to disagree. Defaults (as provided) should be in > /usr/local/spamassassin or /usr/spamassassin (the latter is more for > vendor installs) while local rules/changes should be in /etc/spamassassin > or /etc/mail/spamassassin. The templates file should be in the same dir > as the rules. > There is a religious issue here -- I prefer my add on software not to be installed in system default locations. But, that's my personal preference. > > I agree that there must be a better way to do what we need, but $Config > is probably not the answer. Perhaps fixpath.pl is the way to go, it just > needs to be expanded and combined with a better make file, that could > prompt the user for information. > I'm out of my league here as I don't know much about writing perl installation files. However, perl already provides built-in support for allowing clean installs to local configuration, and I think it makes sense to use those standard options. -- Timothy Demarest ArrayComm, Inc. [EMAIL PROTECTED] 2480 North 1st Street, Suite 200 http://www.arraycomm.com San Jose, CA 95131 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
