I have to supply Perl on a total of eight machines, all binary
compatible. I don't want to have to build it on each machine, and would
prefer to build it into a svr4 installable package. I have done this
manually for perl5.001m, but it would be nice to automate the process,
and to provide a Perl module to form the basis of an OS-independant
install package.
The main problem is getting a definitive list of the files that are
required. The MAMIFEST has lots of stuff that is not needed after build
time, so that's not much use.
Another option is the installperl and installman programs, with the -n
option to produce a list of actions without actually performing them.
The trouble is that if you have already installed perl, most of the
actions don't get performed if the files haven't changed :-(
The last option is to hack apart installperl and installman & mimic their
operation. I suspect that this is the only realistic option.
I suppose I *could* combine installperl and installman, adding
functionality to support building OS-installable packages. An uninstall
option would be nice (although I'm sure nobody would ever want to
uninstall Perl ;-)
I have a vested interest in doing this - what does the panel think?
Alan Burlison aburlison@cix.compulink.co.uk
compatible. I don't want to have to build it on each machine, and would
prefer to build it into a svr4 installable package. I have done this
manually for perl5.001m, but it would be nice to automate the process,
and to provide a Perl module to form the basis of an OS-independant
install package.
The main problem is getting a definitive list of the files that are
required. The MAMIFEST has lots of stuff that is not needed after build
time, so that's not much use.
Another option is the installperl and installman programs, with the -n
option to produce a list of actions without actually performing them.
The trouble is that if you have already installed perl, most of the
actions don't get performed if the files haven't changed :-(
The last option is to hack apart installperl and installman & mimic their
operation. I suspect that this is the only realistic option.
I suppose I *could* combine installperl and installman, adding
functionality to support building OS-installable packages. An uninstall
option would be nice (although I'm sure nobody would ever want to
uninstall Perl ;-)
I have a vested interest in doing this - what does the panel think?
Alan Burlison aburlison@cix.compulink.co.uk