Re^2: How do you compile PerlIO::gzip for AS Perl 5.10?

If all else fails, I could send you a ppm package for it

Is there anything to stop people uploading PPMs to CPAN?

I've built many modules for x64 that aren't available on any existing repository that I'm aware of, but I don't run a website, so I have nowhere to make them available.

CPAN seems like an obvious choice, but it would be better if wherever they were acted as a repository rather than just a file-store, and I can't see that happening.

Or maybe AS could find a place for user-built PPMs--with appropriate disclaimers of course.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP an inspiration; A true Folk's Guy

Comment on Re^2: How do you compile PerlIO::gzip for AS Perl 5.10?

Replies are listed 'Best First'.
Re^3: How do you compile PerlIO::gzip for AS Perl 5.10? by syphilis (Archbishop) on Sep 25, 2010 at 01:30 UTC
Is there anything to stop people uploading PPMs to CPAN? I don't know. What would the PAUSE server and indexer make of a ppm package ? Is there a way of just sticking a file on CPAN such that PAUSE doesn't try to do the things it does when a source tarball is uploaded ? Even if it could be done, I wouldn't. I regard CPAN as a source repository, and would consider that I had "breached faith" if I started putting binaries there. (Yeah, I know ... it's a rather fuddy-duddy antiquated reason, and not a very good one. Btw, I've no objection to someone else putting Windows binaries on CPAN - it's just something that I myself am not currently prepared to do, even if it is possible.) Besides, I already have access to the Uwinnipeg repo - so I could stick it on there if I wanted to. But as (my perception of) my access to that repo isn't one of "anything goes, open slather", I don't usually put anything there unless: a) it's difficult/tedious to build, and b) I'm prepared to update it regularly. I must admit that there are some modules that I've placed on the Uwinnipeg repo that don't get updated as regularly as they should :-) ... but that's no reason to add to the list. Of course, offering to email a ppm package is a long way from the ideal situation - especially when someone digs up the offer 6 months down the track, by which time the package has been lost and needs to be re-built (as has happened to me more than once). It would certainly be good if there was some place to which we could just upload ppm packages willy-nilly. Cheers, Rob	[reply]
Re^4: How do you compile PerlIO::gzip for AS Perl 5.10? by BrowserUk (Patriarch) on Sep 25, 2010 at 02:01 UTC
Even if it could be done, I wouldn't. I regard CPAN as a source repository, Ah well. Just a thought. I guess I was taking the word "Comprehensive" too literally.	[reply]
Re^3: How do you compile PerlIO::gzip for AS Perl 5.10? by cdarke (Prior) on Sep 25, 2010 at 09:22 UTC
Is there anything to stop people uploading PPMs to CPAN? The thing that would make me think twice is what are the license implications of distributing a binary - even if there is no statically linked runtime. FOSS licenses have become so complex that I no longer understand them (to tell the truth I probably never did). If I use a Microsoft compiler then all bets are off - it's safer not to. Not sure how ActiveState get around that one. Anyone from AS wish to comment? To be honest though, what people would really like (on Windows) is a .msi file. Many Python modules are available that way, and Rakudo is as well. Any reason why we don't do that with Perl 5 modules?	[reply]
Re^4: How do you compile PerlIO::gzip for AS Perl 5.10? by BrowserUk (Patriarch) on Sep 25, 2010 at 12:56 UTC
Seems to me that provided the source is freely available, the fact that the packages are, for convenience, also available in binary form, is irrelevant. And if it isn't that way, it should be, and the licensing needs fixing. I see no advantage to an .msi over a .ppm. Nor have I ever seen anyone ask for one. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. RIP an inspiration; A true Folk's Guy	[reply]
Re^4: How do you compile PerlIO::gzip for AS Perl 5.10? by Anonymous Monk on Sep 28, 2010 at 00:37 UTC
Any reason why we don't do that with Perl 5 modules? ActiveState//http://strawberryperl.com/ adopted the same approach, single .msi for base install, then maintain with ppm between releases. A .msi for each module is just busy work.	[reply]
Re^4: How do you compile PerlIO::gzip for AS Perl 5.10? by DrWhy (Chaplain) on Sep 27, 2010 at 20:52 UTC
Personally, I like PPM's current incarnation just fine and see no need for Windows Perl modules to be distrubuted as .msi's. But that's just me. I can definitely see some people, especially Windows admin types wanting to handle Perl module installation that same way the do all other software on their system, with .msi files. --DrWhy "If God had meant for us to think for ourselves he would have given us brains. Oh, wait..."	[reply]