I personally don't like the premise of trying to place artificial limits on how anyone uses this sim. Even trying to do so feels like an insult to the basic idea behind the GPL. If someone received a binary copy of the sim and felt like modifying it with a hex editor, that's their right, and I don't think we should include code to try to prevent it.
I think you are doing the right thing in removing this code. Now that I have that off my chest, I don't really object to doing some basic trademark/name/reputation protection so long as doing so doesn't impede the user's experience. A valid modification to your premise would be to tag the binary with a checksum of the completed build and have the code check that the running binary matches it. If it doesn't then output a simple and unintrusive message indicating the binary has been modified and the URL to the flightgear site to get an official copy. Think along the lines of the Linux kernel tainted module message. It doesn't prevent usage, it just notifies. We'd just be adding a helpful link to the official project site. Though, honestly, I feel even doing that much is wasting time that would be better spent on fixing bugs or adding features. I'm currently working on adding hurricane simulation to the weather system in FG as my first contribution, so until then my opinion on this is worth jack =P Bob -- Delusional Mail (http://www.delusionalmind.com) ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
