On Wed, 6 Dec 2000, brian moseley wrote:
[...]
> this is how we ship our products internally at cpth. we
> build perl, apache, 100 or so modules, and ~150 registry
> scripts. then we rpm the whole thing up. the operations team
> just has to:
>
> rpm -i && /usr/local/webmail/current/bin/wmctl start.
that's what we do at ValueClick too, (except using a tiny script
that configures a perforce view and does a perforce sync instead of
the rpm).
> doing something like that doesn't play nice with the os
> vendor distributions really, but some people might like it.
for applications that are complex enough[tm] it makes sense to
install your own perl, apache, everything. For everything else it's
bloat and just a waste.
> another option would be to use autoconf. wrap a configure
> script around your entire set of components. allow it to
> find and use whichever ones you've already got installed.
> have it build and install whatever you don't already have.
> not very tough. also not very portable to windows.
and doesn't work (or get's complex fast) if it needs, say,
/usr/bin/perl but with -Duselargefiles and the already installed
stuff needs it without.
- ask
--
ask bjoern hansen - <http://ask.netcetera.dk/>
more than 70M impressions per day, <http://valueclick.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
