On Mon, 12 Jul 2004, Steve Hay wrote:
> Randy Kobes wrote:
[ .. ]
> >I compiled my perl too, although using the sources
> >ActiveState provides (for build 810, based on 5.8.4).
> >
> Are you distributing your Perl build in any way?
>
> If you are, then I think you have to hack around the
> ActivePerl source to remove all mention of ActivePerl and
> ActiveState or else get a redistribution agreement with
> them - you aren't allowed to distribute something calling
> itself ActivePerl otherwise. I had a discussion with Jan
> Dubois about this a while ago. I have the mails somewhere
> if you're interested.
>
> Here at Radan we distribute our Perl build with our software, and went
> through a phase of using the ActivePerl sources, suitably hacked to
> remove the Active* name. (At the time that consisted of deleting
> BuildInfo.h, editing perlexe.rc and perldll.rc, and removing
> BuildNumber() from win32/win32.c.) Now that the standard Perl is coming
> out much more frequently itself (and recently there has only been one
> ActivePerl release per Perl release), we don't bother any more and
> currently just use the standard Perl source.
Thanks, Steve - I would be interested in seeing those emails
with Jan, if they're handy.
I am distributing a Perl/Apache binary through
www.apache.org, with Perl built with the ActivePerl sources.
I didn't go to the extent that you did though in doing this;
I just modified BuildInfo.h to read
"based on sources provided by ActiveState ..."
I had thought, based on
http://aspn.activestate.com/ASPN/docs/ActivePerl/Copyright.html
saying that the source code for the modified Perl
distribution used in ActivePerl is distributed under the
same terms as Perl itself, that this was OK. There are
additional proprietary modules contained in the ActivePerl
binary package that aren't in these sources (doc building
tools, ppm, ...), but I'm not including these in the binary
I make (the ppm package I use is an older one from CPAN).
However, it doesn't sound too difficult to do what you
did - I certainly don't want to risk souring our good
relations with ActiveState (however, I suppose some
notice must appear somewhere that the binary is made
based on modified sources?)
I agree that the need for using the ActivePerl sources is
becoming less as Perl's release cycle is more frequent. Even
so, I'll probably still use the ActivePerl sources, as they
change the defaults in the build to define NO_HASH_SEED, and
related stuff - this is useful for binary compatibility
(within 5.8.x) for ppm packages compatible with ActivePerl
(particularly mod_perl).
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
