Re: [RFC] Distributing Windows binary package compiled with non gpl code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 27 Dec 2007, Marco Costalba wrote:

> Packaged together with qgit.exe there are the necessary Micorsoft
> Visual C dll's. Is this a problem for someone?

It depends on how they're packaged together. If it's possible to unpack 
them (into a bunch of separate files, where each is either all GPL or no 
GPL), then this is "mere aggregation" and perfectly fine (assuming you're 
allowed to distribute the Visual C dlls, of course). IIRC, bundled 
libraries for Windows programs are stored on the user's disk as separate 
files anyway, so this is automatically okay.

I'd actually be more concerned about whether you can (or should) 
distribute GPL code compiled with a proprietary compiler; people who get 
the binaries and the source still couldn't edit the source and generate a 
corresponding binary, because they don't necessarily have the build 
environment you used. On the other hand, nothing you could do differently 
would be any better for anyone with the right to complain, so it shouldn't 
be an issue in practice. (And a user of qgit for Windows is more likely 
than usual to have MSVC anyway)

	-Daniel
*This .sig left intentionally blank*
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux