On Tue, 2008-30-12 at 13:32 +0000, Hans Salvisberg wrote: > What's the difference between installing qpsmtpd as in... > > perl Makefile.PL > make > make test > make install
Two problems: 1. Scripts "use lib 'lib';" so you will need to modify them on install. 2. The config directory will also be lost. Makefile.PL [1] supports running things through a filter on install so you can easily fix (1) -- except I'm not sure that how easy it is to pass in the installed library location (I have an example but it makes arbitrary code changes and does not use perl variables). A third problem is that the default configuration probably does not do anything useful for you. I haven't been messing with qpsmtpd for the past year but when I get back to it, what I'd like to look at is an interactive config/install script. There's also Build.PL [2] and Module::Install [3] but I don't think any of the perl auto-builders solve this problem yet. [1] I.e. ExtUtils::MakeMaker [2] I.e. Module::Build, iirc. [3] Not as widely used. > make clean > > ... or running it directly from /home/smtpd/qpsmtpd? > > Presently I'm running ./qpsmtpd from xinetd, so the installed copy is > probably wasted, right? > > Is there any benefit/downside in running an installed copy, and how would I > do that? > > Hans > > > -- --gh
