Garrett Rooney writes:
> On 5/21/06, Peter N. Lundblad <peter@famlundblad.se> wrote:
> > Garrett Rooney writes:
> > > On 5/19/06, Giovanni Bajo <rasky@develer.com> wrote:
> > > > Hello,
> > > >
> > > > I was wondering if it would make sense to ship a binary version of svnmerge.py
> > > > in the Windows binary pack. I can easily provide a standalone executable that
> > > > works without Python installed. But I have no clue how the packaging process
> > > > works, so if there is agreement that this is a good thing to do, I would need
> > > > instructions on how to proceed to make it happen (too late for 1.4.0?)
> > >
> > > I'm not overly thrilled with the idea of shipping a GPLed script in
> > > our installer. At this point, all the functionality we ship is under
> > > a BSDish license (well, with the exception of the bdb filesystem, but
> > > you can leave that out), if we start shipping svnmerge.py all of a
> >
> > What we're discussing here is the binary Windows distribution, in
> > which we don't leave bdb out, so I don't understand the above.
>
> Sure, but with sufficient hacking we could leave it out, and no user
> visible functionality would be missing.
>
After some IRC discussion, I agree that we should be careful with distributing
GPLed software in our binary distributions. I think it would be
better if the svnmerge binary was distributed separately with a link
to it somewhere on our site.
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 21 20:48:28 2006