This is why package management systems such as deb, RPM, ports, and so on were invented. The software could be built once and installed many times. There was even one available for Solaris!. For example, both Fedora and Ubuntu have over 3000 perl modules waiting to be installed.
| [reply] |
| [reply] |
| [reply] |
I never, ever allow anything to come remotely close to my system perl (or python etc).
Why? If the vendors repo for the system perl has modules, those were compiled and tested with the system perl and just work, just like they would with any custom perl installed with e.g. perlbrew.
For years I have just used the system perl and the system build system to compile and install modules (as *.deb, *.rpm, you name it) not present in the vendor's repo, with no adverse effect to the system perl or the system itself.
The system perl often comes along with patches (Debian for instance has a long patchlist) which are probably optimizing perl for the system at hand. If I were to compile the same perl version with the systems compiler, its libraries and those patches, it would be no different from the system perl.
And there is always local::lib.
perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
| [reply] |
run a VM locally the same OS and architecture as your target
Therein lies the difficulty...I have no idea of either the OS (other than Linux) or architecture of the target virtual machine.
It is not something I am going to spend much time on.
When it becomes mission critical, and when my Linux confidence improves, I will upgrade to VPS or dedicated server which will make the issue obsolete.
| [reply] |
| [reply] |
As you yourself said marto in Re^10: Perlbrew on shared hosting
As your skills develop no doubt you'll consider alternatives
As yet, those skills haven't developed sufficiently. Instead I've been implementing templating and replacing require *.pl; with modules.
Probably more useful skills to me than learning to identify the architecture of a virtual machine that will be replaced before very long with one of known architecture and over which I have more control.
| [reply]
[d/l] |
