Re: using Perl to look for GPL code in M$ OS binary/source?

Beatnik already pointed out several problems with your approach, but since we're on the topic of GPL violations...

Have you ever used a GPL'd module in your code and not released the code in a GPL-compatible way? As I pointed out in Re: Re: GNU GPL & Commercial Scripts, this is a violation of the GPL. Just something to consider.

Also, referring to Microsoft as M$ does not help your argument.

Comment on Re: using Perl to look for GPL code in M$ OS binary/source?

Replies are listed 'Best First'.
Re: Re: using Perl to look for GPL code in M$ OS binary/source? by mojotoad (Monsignor) on May 09, 2002 at 16:21 UTC
The emphasis should be more on released applications rather than commercial status -- my understanding has always been that if you are not providing the application to the public (for profit or otherwise) then there is no violation. After all, if you can't get your hands on the application, why should you expect access to the code? Put another way -- there is no violation pre-release. If you never release, there is never a violation. If you never release beyond in-house, there is still no violation. Profit is irrelevant to that dynamic. Matt	[reply]

Replies are listed 'Best First'.

Re: Re: using Perl to look for GPL code in M$ OS binary/source?
by mojotoad (Monsignor) on May 09, 2002 at 16:21 UTC

released

commercial

Put another way -- there is no violation pre-release. If you never release, there is never a violation. If you never release beyond in-house, there is still no violation. Profit is irrelevant to that dynamic.

Matt

[reply]