jplindstrom has asked for the wisdom of the Perl Monks concerning the following question:

Regarding this comment about the PAR ActiveState PPM being a little dated, does anyone know the procedure to get a CPAN module to appear in ActiveState's PPM repository?

I always thought it was just a matter of getting the module to build successfully and pass it's tests, and everything else would just, well, work.

Can anyone confirm this, or give me a hint on how it actually works?

/J

Update:

Thanks for the advice given below, but this is in regard to an existing module (Win32::GUI) which already has an old PPM in the repository. It's a real problem that most people get the obsolete version, so when a newer version becomes available on CPAN it would be nice to get the ActiveState repository updated.

Replies are listed 'Best First'.
Re: What makes PPMs appear on ActiveState?
by PodMaster (Abbot) on Nov 09, 2004 at 19:31 UTC
    Like I link to in my repository README, http://aspn.activestate.com/ASPN/Downloads/ActivePerl/PPM/
    Requesting PPM support for a particular package.
    For support please email ActiveState at ppm-request@ActiveState.com Most requests for new modules can be fulfilled provided the module builds, and passes its own test suite.
    If you want more detail than that you need to ask ActiveState (and/or maybe look on their mailing list archives first).

    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.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]
      Excellent, that's exactly what I asked for! Thanks!

      /J

[reply]
Re: What makes PPMs appear on ActiveState?
by bibliophile (Prior) on Nov 09, 2004 at 19:04 UTC
    I'm not sure how the whole ActiveState PPM thing updates, but here are some links on building your own:

    ActiveState FAQ (also lists other PPM repositories)

    and the monkish aspect:

    How to build...

    Hope that helps :-)

[reply]
Re: What makes PPMs appear on ActiveState?
by Grygonos (Chaplain) on Nov 09, 2004 at 19:05 UTC

    You can run your own ppm repository as PodMaster does and add the repository to your source repositories in ppm. I don't know many specifics.. but it is doable (have added sources to ppm but forgot how)

    Grygonos
[reply]
Re: What makes PPMs appear on ActiveState?
by jdtoronto (Prior) on Nov 10, 2004 at 04:15 UTC
    PAR obviously has a problem at 0.85 because according to this: module status report from ActiveState it will not build cleanly under their automated system.

    As for Win32::GUI - this has long been a thorny one. The developer maintains his own PPM respository, but even that only has version 0.502! The latest version can be downloaded from the author or it is available from sourceforge as well. In this case the version on CPAN is vastly older than that on ActiveState. But if the developer doesn't release to CPAN then what are ActiveState to do? Go trolling all around the Internet to find the stuff?

    I agree that it is difficult maintaining a Win32 Perl installation, sometimes ya just gotta do some digging yourself.

    jdtoronto

[reply]
      The good news is that Win32::GUI 1.0 is due on CPAN fairly soon so we can leave that mess behind.
[reply]
Re: What makes PPMs appear on ActiveState?
by Anonymous Monk on Nov 09, 2004 at 21:43 UTC
    I think it requests the sacrifice of a small sheep or possibly the payment of an ActiveState license :) There are some questionable choices for PPMs and some notable omissions, so I am pretty sure that's the reason. Really, I don't blame them if that is the model. Makes one sign up to get support.
[reply]
Re: What makes PPMs appear on ActiveState?
by rinceWind (Monsignor) on Nov 10, 2004 at 12:49 UTC
    Regarding this comment about the PAR ActiveState PPM being a little dated, does anyone know the procedure to get a CPAN module to appear in ActiveState's PPM repository?
    I think that the truth is exposed more if you go to the PPM build status pages.

    Many modules are listed as "Fail" owing to prerequisites, or owing to the build needing a manual step.

    In the case of PAR, the Makefile.PL step is asking whether to auto-install Parse::Binary and Win32::Exe. Taking the default of No, tests are failing, or rather timing out.

    Hope this helps.

    --
    I'm Not Just Another Perl Hacker

[reply]

Back to Seekers of Perl Wisdom