>> This was my originally thinking as well, except for #2, which I didn't >> totally think through. I personally think that it would be >> unreasonable to ask commercial software vendors who are writing Haiku >> apps to recompile a non-GPL version of Haiku just so they can produce >> an application whose resulting binary will probably be identical >> either way (yes, i know that's a technicality... but I find this >> absolutley moronic). The #warning should in my opinion be included. I was talking with respect to resellers and redistributers of the OS for other purposes, which may or may not include sale to general public. >> >> If that is going to be an issue, I think I'll switch my opinion to this: >> >> 1) Build Haiku with any GPL code disabled that would otherwise cause >> Haiku libraries which do not contain any GPL code to then become GPL >> >> 2) Produce optional packages containing the GPL addons that a user can >> install manually - or with a future "package manager". >> >> As much as I think step 2 becomes a PITA, it even encourages someone >> to write a non-GPL version of those addons in the future if they so >> desire (hint hint!) ha ha ha... >> On the other hand, perhaps we make two distributions of Haiku >> avaialble: "Haiku alpha 1 Standard" and "Haiku alpha 1 GPL-E" (E can >> stand for either "Enhanced" or "Encumbered" depending on your >> viewpoint ;) I don't think you got my point, about resellers and redistributers of the OS for other purposes, which may or may not include sale to general public. :)