You can choose to distribute Perl under either the Artistic License or the GPL. I assume that you're distributing commercially.
The GPL will allow you to either include source code in your distribution, or to include an offer, good for at least 3 years, to distribute full source code. You are not allowed to just point to where source code is available, though, because your distribution is commercial. (Many people overlook this fact.)
The Artistic License will allow you to distribute if you include source, change the names of the executables and document differences, embed Perl in some program so that it is not externally visible, or make other arrangements with the copyright holders. (The last option is virtually impossible, don't try it.)
So the full list of ways that you can get permission include:
- Include source
- Include an offer for source, good for 3 years
- Change the names of the executables and document the differences from the standard
- Embed Perl so that it is not externally visible
- Make other arrangements with copyright holders (this ain't happening, sorry)
Do any of these things and you should be fine. Do none, and you're violating copyright law.
I am not a lawyer, this is not legal advice, yada yada yada. (Technical note, by saying that I'm saying that if you follow my advice and get sued, you can't sue me for giving you bad advice. This is why lawyers WILL NOT give legal advice without being paid, because legal advice has liability associated with it.) | [reply] [Watch: Dir/Any] |
Yes
Look at PAR for one open-source solution
ActiveState offer PerlApp in the Perl Developers Kit, as a commercial alternative (the one I use)
perl2exe can be found here and is another commercial alternative.
jdtoronto | [reply] [Watch: Dir/Any] [d/l] |
I believe the question was more about distributing a core perl installation (though in some sense that's what the solutions you're proposing are too). If I understand correctly it kind of depends whether or not you can do that. For example, I don't think you can just redistribute ActivePerl, but with other builds (including your own) you usually can.
(Please correct me if I'm wrong on this.)
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] [d/l] |
| [reply] [Watch: Dir/Any] |
I indeed want to redistribute Perl itself commercially together with my scripts which are in source. Looking at the comments this should not be a problem as long as I pick the right distribution.
I am not sure at this point if the ActiveState ActivePerl distribution is within this category.
Thank you all for the quick comments!
Robert | [reply] [Watch: Dir/Any] |
If you do a little bit of work during development, you can ensure that your applications work with the version the current "latest" Perl - or better yet, based off of 5.6.1. It just seems like a huge, unecessary burden to make sure the client is using *your* version of Perl. If someone gave me an app + the Perl he wanted me to use, I most certainly no install his Perl...in fact, I'd just use my own rather than have multiple versions of Perl floating around on my machine (especially if it was a windoze box).
| [reply] [Watch: Dir/Any] |