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

Hey guys!

I'm not much of Perl programmer, but I do have one module on CPAN. I recently updated it (after couple of years) -- there were a few consecutive updates (0.07, 0.08, and 0.09) a couple of days or so apart, as I was messing up POD & packaging. But I think I finally got everything together right in ver 0.09.

Then I see 0.09 doesn't show up in my Active State PPM. 7&8 did before, and CPAN has 0.09.

Looked up on http://code.activestate.com/ppm/WWW-Yandex-Catalog-LookupSite/ and version 0.09 has lock icon on it that says "This package requires a valid Business Edition license".

Anyone knows why that would be? The only change between 0.08 and 0.09 was in documentation, there was no code change.

UPDATE: it was a problem on PPM servers, and they had to manually update bits to fix it after my post.

  • Comment on ActiveState: Package required Business License

Replies are listed 'Best First'.
Re: ActiveState: Package required Business License
by davido (Cardinal) on Jul 24, 2012 at 17:41 UTC

    The good news is that there is nothing particularly complex about your module's composition that would prevent it from being installed the conventional way on ActivePerl using the standard CPAN tools (cpan, or cpanm for example). PPM support is most useful for modules that require difficult compilation. Your users have the alternative of just using the same install technique that non-ActiveState users employ.

    If you think that Community Edition ActivePerl users might comprise a significant portion of your module's user base, you might consider adding an INSTALL file to the distribution that discusses ActivePerl installation options, or add a blurb to the README.


    Dave

Re: ActiveState: Package required Business License
by Anonymous Monk on Jul 24, 2012 at 19:03 UTC
    ActiveState has been having revenue problems lately, and the "pro bono" days of maintaining their alternative packaging system are probably gone for good. You get with AS a much more "Windows-like" experience but you are going to wind up paying a share of the staff costs involved. If that does not suit you, there's always Strawberry.
Re: ActiveState: Package required Business License
by bulk88 (Priest) on Jul 24, 2012 at 23:44 UTC
    That is interesting. I thought AS only charges for their proprietary unix builds (Solaris, HPUX, AIX). Is AS tagging by hand "hot" modules for Business License or is there a proprietary window (days/weeks/months) until a ppm package goes free? Or is it a bug with the website that until the archive/build log moves from the build system to the website the lock icon stays on because its really a "not found" in the database? With my experiance with AS's PPM build servers, they recognize the new release in 24-48 hours, it gets a red or green button but the build log links of the new release are all 404 not found for 1-3 more days. Maybe the build log 404 bug is now a lock icon? I would like to see this mystery solved.

      Fixed. It was a problem on PPM servers, and they had to manually update bits to fix it after my post on AS forum.

        Thanks for an answer and it is good to know it was simply a bug in AS's system, not a new business model at AS. Its over 1 month later BTW. I lost hope on getting an answer a long time ago :-)

      I would like to see this mystery solved.

      :) thats not likely to happen at perlmonks :)

Re: ActiveState: Package required Business License
by bulk88 (Priest) on Jul 26, 2012 at 20:21 UTC
    For what its worth, in the PPM GUI program included with ActivePerl 5.12, I only see 0.08 listed, not 0.09, so its truly blocked, not just on the website.
Re: ActiveState: Package required Business License
by zentara (Cardinal) on Jul 24, 2012 at 16:47 UTC
    package requires a valid Business Edition license

    Pop in a Linux cd and forget about it all.


    I'm not really a human, but I play one on earth.
    Old Perl Programmer Haiku ................... flash japh
      Or just install with cpanp ;)