> On Wed, 30 Jul 2003 11:59, Clayton, Nik [IT] wrote:
> > > we are talking about the times where interactivity is a must.
> > > i'd be interested to know how you'd make cpanplus' install
> > > non-interactive for example.
> >
> > Any time you have a large site with multiple hosts, all of which must
> > have the same version of the package installed with the same options.
>
> That's what OS packages are for.
So what if you're the person trying to build the packages for the OS?
This is something I do almost daily, and I've got it down to a fine art on
Solaris. I pretty much just need to create a Makefile with
PERL_MOD= yes
.include "/path/to/some/magic.mk"
and it DWIMs everything for me, calling "perl Makefile.PL" with all the
necessary options to install the module in a private install/ tree,
and generate a complete Solaris package from that install/ tree. Unless
the module refuses to believe that it's going to be run on any host other
than the one "make install" might be run on, and refuses to install if
the environment doesn't look right (e.g., particular UIDs not existing
on the build box, or certain directories in /var not being present).
If there's no way to smack the module in to submission with a few
environment variables, which I could define in the Makefile with a line
like
CONFIGURE_ENV= JUST_INSTALL_DAMN_YOU=yes
then I've got to go and edit the source code. Which introduces local
changes, which need to be inspected every time we upgrade a module.
This isn't a problem that's confined to some Perl modules, obviously,
but it's still annoying.
This is Unix. The system should know enough to get out of my way if I
know what I'm doing.
N
--
1 1 2 3 4 5 6 7 7
0 0 0 0 0 0 0 5
-- The 75 column-ometer
Global Messaging, A: Top posting
120 Cheapside, x83331 Q: What's the most annoying e-mail habit?
