Partly the reason this stuff can't be fixed is that it can't be fixed.

I spent a YEAR trying to get my modules (most of which need refaddr via deps) supported in the PPM build system, to no available.

I even spoke to them IN PERSON, was assured something would be worked out, and eventually got to the position at the end of the day that some of the technical bugs in the PPM system CAN'T be fixed due to commercial reasons.

Likewise, they can't bundle GCC with Perl like Vanilla/Strawberry does due to licensing conflicts, with those licenses there for commercial reasons.

So after a year of trying, I simply concluded that depsite their previous good works, which I appreciate, ActiveState has now reached the point of damaging Perl. That's nothing against the individuals involved, just that ActivePerl appears to me to have worked itself into a commercial and legal position that is untenable.

And so I decided to, like the internet, route around it and just make a "normal" Win32 Perl distribution that removed the commercial constraints and did things the way I was used to having them on Unix.

And the end result after the help of dozens of awesome volunteers was Strawberry.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.