- ACTIVEPERL OFFLINE INSTALLER HOW TO
- ACTIVEPERL OFFLINE INSTALLER INSTALL
- ACTIVEPERL OFFLINE INSTALLER PORTABLE
Developers are going to have a much easier time making things work how they want since they're generally more technically inclined to begin with.Īs for Command Prompt Portable if I do this I would definitely add a check for that, and probably Console Portable as well with an ini option to set the default. Personally I think it's better to cater to casual users. Clear concise directions (or even a perl script) could be provided if the PortablePerl.exe cmd shell launcher was available from the menu, whereas otherwise the directions would include having to delve into the directory structure of CommonFiles to do the same.
ACTIVEPERL OFFLINE INSTALLER INSTALL
For instance I can see this being used by non-developers when they need to install a new CPAN module for use with a portable app. If you split it up then you gain compatibility with those features and it makes it easier to explain things to non-developers. If things are kept "easy" and all thrown in CommonFiles\Perl (Jimbo's first post) then you lose compatibility with PAF backup programs that backup data, interoperability the PAM menu, etc since everything in CommonFiles is ignored. The entire strawberry distribution is over 120MB.Īnyone want to chime in with their opinion, or have a better idea?
The Perl folder is 36MB, or about 31 when compressed. Unfortunately this method precludes using Portable (strawberry) Perl fully to compile new modules. This would allow us to standardize on CommonFiles\Perl in Portable Apps that require Perl, and users could either use our package or drop in ActivePerl if they like. My thought is that for Portable perl using Strawberry perl we should probably only include the Perl folder. As long as you have the required modules in each, you can use either to run perl scripts. The two Perl folders are interchangeable, and are all that are required to run perl scripts.
+-(other AP specific folders not used when running scripts) The way Strawberry perl is set up to handle this with a folder structure like this: Of course ActivePerl isn't open source so we can't include it (yet.) but we probably shouldn't actively preclude it from working either. Compiling isn't for the meek, but pre-compiled packages means you're waiting on someone else to do the work for you. ActivePerl's method of dealing with modules is to instead include a package manager which downloads pre-compiled modules from known repositories instead of compiling as needed. This makes it work nearly exactly like every other version of Perl out there except ActivePerl. Strawberry perl includes not only perl, but enough of MinGW to also compile CPAN modules.
ACTIVEPERL OFFLINE INSTALLER HOW TO
Here's a little background on how strawberry perl is set up followed by my opinions on how to proceed: The intention of this is for it to be placed in CommonFiles for use by other portable apps, like portablized Java is now. This will perform the required configuration. For example, cpanm IPC-System-Simple-1.21.tar.gz. Then, install the distribution by passing its file name to cpanm. I'm in the process of putting together a portable build of Perl based on the fully open source Strawberry Perl distribution. First, install cpanm if you dont already have it.
0 kommentar(er)
