On Sun, Apr 14, 2002 at 06:56:08PM -0700, Bart Schaefer wrote:
> On Sun, 14 Apr 2002, dman wrote:
>
> > | 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.
>
> MakeMaker is for building perl modules. Perl modules are supposed to keep
> their configurations in the usual perl places.
>
> (I'd wager that even on Debian you'll find "host-specific configuration"
> in /usr/lib/perl5/site_perl/<version-number>/Net/Config.pm, and not find a
> Config.pm anywhere under /etc.)
If it wasn't in /etc, I'd file a bug.
daf@green:~$ ls -al /etc/Net/Config.pm
-rw-r--r-- 1 root root 7513 Dec 16 18:07 /etc/Net/Config.pm
daf@green:~$ ls -al /usr/share/perl5/Net/Config.pm
lrwxrwxrwx 1 root root 18 Apr 14 14:09 /usr/share/perl5/Net/Config.pm
-> /etc/Net/Config.pm
>
> > 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).
>
> That doesn't work either, because all the other perlish things that SA
> relies upon are going to expect things to be in $(PREFIX)/, not in
> $(PREFIX)/../. And as I said, MakeMaker is going to generate install
> rules that use $(PREFIX)/. $(LOCAL_RULES_DIR) is a special case only
> because SA's Makefile.PL includes an explicit rule for it.
>
> All I'm trying to accomplish -- and I wouldn't have thought it would need
> this much discussion -- is to make SA be a well-behaved perl module (more
> specifically, a well-behaved CPAN module), that can be built by an un-
> privileged user in the same way any other well-behaved perl module would
> be built by that user.
I see your point.
> If that's impossible, whether politically or technically, then SA should
> be withdrawn from CPAN.
No objections here.
Perhaps we could build a second package for use on CPAN, that would contain
messed up paths (and local config in $(PREFIX)/etc )?
I've stopped caring. It doesn't affect me.
--
Duncan
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
