Release obfuscated GPL code?

Question

The rationale of the GPL is that I must release my source code changes with the binary release. Suppose I obfuscate the hell out of my code, compile the obfuscated code into a binary. Then the source code that goes with the binary is the obfuscated version. Seems like this would be in compliance with the GPL.

Answer 1

sounds like a joke.

first, for this "legal" doubts, ask a fsf lawyer.

second, there's no difference in binary produced by the obfuscated code and the cleaned (from obfuscated) code; it is just a stupid step you put without reason.



i believe also it would be in contrast with the gpl, because the real aim of the whole thing is to give other people the right to see and modify the code, under some rules and circumstances. the preamble to this right is the condition of the code to be understandable.



casual bad code hardly understandable can be written; making it not understandable intentionally is like trying to kill the right the gpl exists for.

Answer 2

Having just discovered SlackBuilds (shell scripts which make Slackware install packages from source the way Gentoo does) I can assure you that there is a legitimate reason for releasing the source code -- specifically so anyone can modify or optimize it as they please. Ironically I also understand the Mozilla Foundation's position with the Debian Developers -- they decided that Debian was wringing too many changes in the programs to permit them to release them as Firefox or Seamonkey, so Firefox was suddenly releasing Iceweasel (firefox) and Iceape (seamonkey). If you don't want to release your program as GPL then think of it this way: if you can take your program and compile it on C++ Codebuilder, or Visual C++ or Digital Mars's Compiler, then you don't have to release the source code UNLESS it REQUIRES GPL

d libraries. This was something Steve Jobs ran into back at NeXT Computers with Object C. Don't use GPL'd libraries, you can GPL it or not as you wish. Use GPL'd libraries, release it as Open Source or risk our curses (-l lcurses). If you want to obfuscate it, then submit it to the International Obfuscated C contest or else expect that some people will make a contest out of un-obfuscating it.



http://www.ioccc.org/



Tizio 008, check out my link.

Answer 3

If you obfuscate your code you will have trouble maintaining it in the future, yourself.



If you keep an unobfuscated version of it for your own use, you may be considered to not have released the source with the binary, but a processed version of it. You would have to check some more on that.



But what is your motive of doing what you described, really?

Answer 4

Been programming for over 15 years and that i've got on no account seen something that facilitates you to write obfuscated code (nicely, something that works besides, ;->). you always use a application to obfuscate the code once you have written it.