in reply to The quest for pure perl

Having had similar problems, I sympathise.

Perhaps, we could set up a single thread in say categeriszed answers under a question of "What pure perl modules are available" and everytime a conciencious Monk pull a module, they could post a one-line answer with a link to the module they found to be perl only, having checked that it hadn't already been listed 27,000 times:)

Seems like a simple machanism that would be of great reference value and need no infra-structure changes to set up?

As far as the Win32 stuff is concerned, it is possible to build XS modules to be compatible with AS. PodMaster seems to have the wherewithall for doing it, but it does seem like an imposition to have to ask someone else to do it for you. I'm not sure what loops PodMaster has to jump through to make this happen, but it seems a shame that AS themselves can't set up some sort of post-the-url-to-a-CPAN-style-tarball and-our-auto-build-robot-will-attempt-to-build-it-for-you page at their website. It could report back the results/errors from the attempt and if successful, add it to the appropriate PPM directory on their download site. Hmmm. Anyone got an AS support contract fancy forwarding that as a suggestion? I doubt it would make it past the small-round filing cabinet if it came from anyone without one.

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

Replies are listed 'Best First'.
Re2: The quest for pure perl
by bbfu (Curate) on Feb 19, 2003 at 15:44 UTC

    but it seems a shame that AS themselves can't set up some sort of post-the-url-to-a-CPAN-style-tarball and-our-auto-build-robot-will-attempt-to-build-it-for-you page at their website.

    Unfortunately, that would require allowing arbitrary code (Makefile.PL) to be executed on that server, by anyone. I think that would be too large of a security risk for them to want to maintain that machine.

    bbfu
    Black flowers blossum
    Fearless on my breath

[reply]

      Your probably right.

      I keep thinking to myself that given the right set of limited permissions for a specifically set up userid with no read/write/execute access outside a download/build directory created specifically for each given download and destroyed immediately after the PPM is built, it ought not be a security risk. That said, the only time I set up anything similar (under NT, I wouldn't have a clue under *nix) the aim was prevention of accidents rather protection from deliberate attack.

      Oh well. Another transient thought bites the dust:)

      Examine what is said, not who speaks.

      The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

[reply]
        I am not sure how to do this with Unix, but with Windows using Ghost we could the automate the installation of a fresh OS image and perform an installation (or, whatever operation). We had just about every MS OS flavor. When we were done, we would install another fresh OS image and start another test.

        It seems like it would be possible to isolate a build machine that used a fresh OS image for each build. I am not sure about the implications for doing this in the Unix world.
[reply]

In Section Seekers of Perl Wisdom