Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • I contact the guy that did the PXPerl distro. It is really good already but he is a student looking for money. Hopefully he will apply and be accepted. []
    • Hi, I am the author of PXPerl. I'm indeed interested in this. I am going to (re-)write a proposal to TPF. Perhaps I'll be more successful this time :)
      • Are you planning on resubmitting for PXPerl, or attacking this by starting from Vanilla and going from there.

        Because in trying to work on PXPerl's build stuff, before we had to abandon it and look for fresh approachs, I was getting comments that some of it was doing some very crazy and evil thing.

        One of the key points of my challenge to find a replacement for PXPerl was that it had to be reproducable. Someone else needed to be able to come along and keep maintaining it, so that we didn't suffer from the ris
        • by gpean (6826) on 2006.04.03 6:54 (#46930)
          I am completely aware of what PXPerl is lacking: everything is made by hand and that's definitely not convenient nor contributable nor reproducable. But when I started PXPerl, I just didn't want to start another more ambitious project that I would forsake 2 months later, unfinished.
          The current drawback is that, justly, practically no one can contribute to it, and anyway I don't want to because it's way too crafty (and I am curious about your "evil" thing... I haven't had such feedback).

          Given that, I started a big automated build script (with enhanced chained modules installation etc.) for PXPerl, so that everyone would be able to make its own PXPerl at home, and so that everyone can contribute to it.
          It is perhaps 60% finished, but I quite stopped creating it in november of last year.
          Perhaps some parts could serve for Strawberry Perl...

          It is a pity that TPF didn't even contact me or replied me to my grant request. No answer to why my application was rejected, no encouragement, nothing. Now it's fostering a brand new project, with quite exactly the same goals as PXPerl... I hope at least that I contributed to the idea, or to show that people were needing this.

          So, no, I won't make PXPerl a concurrent to Strawberry Perl, which is more clean. I am currently in fog as regards PXPerl. I am tempted to put an end to it, in an official manner, because I haven't done anything for it since a couple of months. I guess that with the announce of this new project, the decision will be more easy.

          Now, as regards my application for Strawberry Perl, I am wondering how much time do you expect from an applicant for this, eg. monthly (bounds)? How does the grant allocation work for this kind of "job"? per hour, per task? I guess that you will be choosing the one that request the smallest amount in the application form.
          • I believe some of the comments I got mentioned some really ugly hardcoded build paths, that might it very difficult to even reverse engineer the improvements to it.

            I wouldn't be too surprised that you didn't hear, the rule of complaints is that you only ever hear 1 out of 10 in any case, and I don't know of more than 3 or 4 people that looked at the internals.

            PXPerl certainly helped I think, there's nothing like having a prize laid out before you, almost completed, and then have it snatched away, to drive p