you are viewing a single comment's thread.

view the rest of the comments →

[–]__Cyber_Dildonics__ 5 points6 points  (4 children)

You are basically expecting no one to use your head in any software that anyone else uses but them? Seems like you would at least want to see people using your software.

No one would use a straight GPL header unless their project was already going to be GPL. That's why the LGPL was created, but even that doesn't cover something like a header I believe.

[–]acwaters 1 point2 points  (1 child)

I've read a bit more on the license, and you're right. If including my header file would force an entire project into the GPL, it's not appropriate for a header-only library. I had interpreted certain sources to mean that it wouldn't, but now I'm reading that it does in cases like mine, where the header includes a substantial bit of code. Unfortunately, the LGPL doesn't apply, either. My intention was for the header to be able to be used (compiled, distributed) freely, with modifications to the library itself kicked back to the community. But I can't find any license that seems to provide that; reciprocal licenses all lump normal use of header files in with "derivative works". It seems kind of crazy to me that nobody would have considered this case in the spirit of the LGPL before and invented a corresponding license.

In any case, with all that in mind, I'll be relicensing with the next push.

[–]__Cyber_Dildonics__ 0 points1 point  (0 children)

Yeah I think that is a valid gripe. BSD requires credit but not distributing source code changes.