Re: The quest for pure perl

[PodMaster]

What about PPM? (you ain't building it)

MSVC on Win32 requires some setting up to make it usable -- not true.

Mirror CPAN, and build the a database containing such metainfo (you'll have to figure out how to determine what's what on your own, but it should be easy, scan for *.c, *.xs, *.h files, check the registered module list, since all registered modules have this info, but beware of dependencies ).

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy.

[rinceWind]

In my case, the required platform is Solaris. OK, I know that ActiveState provide builds for this platform, but the underlying perl build on my target machine is not one that AS supplied, but one that came with Solaris, hence PPM is not an option. The siteperl directories exist, but are empty.

I only mentioned Win32 because of some difficulties I have been having at home.

(...beware of dependencies)

I couldn't agree more. Just because module A is pure perl, if it calls module B which needs XS, this is no good. Ideally, I am looking for something that can build a prerequisite requirements tree, flagging any modules that require an XS build.

[jepri]

Head over to http://www.sunfreeware.com/, grab a binary of GCC, install it in your home directory, edit your PATH, INCLUDE, and LD_LIBRARY_PATH shell variables and get cracking.

There's also a tutorial around somewhere that gives you instructions on how to install Perl modules into your home directory.

Finally, don't forget that most Sun machines are binary compatible, so you can compile modules on your dinky Ultra workstation and upload them to your enterprise servers, where they will work just fine.

____________________
Jeremy
I didn't believe in evil until I dated it.

[PodMaster]

OK, I know that ActiveState provide builds for this platform, but the underlying perl build on my target machine is not one that AS supplied, but one that came with Solaris, hence PPM is not an option

How so? Sure, AS might not make binaires for you, so all that means is that you have to make binaries for you. You know how your perl was built, so duplicate the build environment, and build the extensions, and make the PPM packages. Many-a-monk do this.

As for dependencies, the question has come up a few times here on perlmonks, so do a search. The following modules should be of interest: Module::Dependency, Module::ScanDeps, Module::CoreList, Module::Info, ExtUtils::Installed, ExtUtils::Install

MJD says you can't just make shit up and expect the computer to know what you mean, retardo! I run a Win32 PPM repository for perl 5.6x+5.8x. I take requests. ** The Third rule of perl club is a statement of fact: pod is sexy.