>>>>> "AM" == Andrew McNamara <andrewm@connect.com.au> writes:
AM> In our environment (ISP), applications are built inside a firewall,
AM> then pushed out to "sacrifical" bastion hosts. So... I'd like to be
AM> able to package up mj2 (SVR4/Solaris packages, although I'd imagine RPM
AM> style packages would be similar).
The RPMs of Majordomo1 have been horrible, and are the cause of a large
number of problems that you see in majordomo-users. I don't think packages
are the way to go with this, although SysV packages should at least let you
run a shell script afterwards to ask the appropriate questions. They're
fine for packages even as complex as Emacs, but they don't deal well with
things that require interactivity. Remember that the executables are
generated on the fly according to input data. If you change any of the
source directories, the default domain, the temporary directories, or even
the UID, you have to build the binaries afresh.
So in general I'm going to recommend against doing any such thing because
the installation process is so complex and interactive that I'm not sure a
packager will do everything right. How, for instance, would you make the
wrappers optional? It was difficult enough to get MakeMaker to do it. I
would suggest that you understand everything that's done in Makefile.PL and
postinstall first.
- J<
Follow-Ups:
References:
|
|
