Closed mtdcr closed 7 years ago
How sad to see a makefile being copyrighted; how low can you go :(
It's MIT-Licensed, all you have to do is keep the Copyright and License.
If it was without License, it would be proprietary and you wouldn't be allowed to use it at all.
This is, btw, true for ALL MIT-Licensed code. Common GPLed Projects have all of the code licensed, which includes the Makefiles, configures, et cetera, and there is no problem with that at all.
PS: I don't see any need in discussing this further, as it's already been merged PPS: Thx arn354 for merging PPPS: sorry for editing it a million times
I originally took the fork from OpenPLi, so you better go tell them too https://github.com/OpenPLi/openpli-oe-core/blob/master/Makefile
It is not just limited to Makefile .. why not praise all the work you did andyblac?
as I said, I forked from PLi not him, I honoured their git, we are under no agreement with the other git, that's down to where PLi got the code, and who to say they did not come up with this similar makefile all by themselves.
also, the make file is just a bunch of BitBake variables, and you can't copyright what is not yours IMO.
so unless PLi add this pull request as well, it should be reverted.
Dear oe-alliance developers,
your Makefile is a fork of the opendreambox Makefile with copyright information and license terms removed - which is a violation of this license (MIT).
For your reference, here's the first published version of the original Makefile I wrote for opendreambox 2.0: http://git.opendreambox.org/?p=opendreambox.git;a=blob;f=Makefile;h=44f7e8790b77cff86d737d957b92595a9c03cf36;hb=06c139ede3555f59b051917b599133cc9fae033f
And this is the first commit of oe-alliance, which landed about one month later: https://github.com/oe-alliance/build-enviroment/blob/2d104e7a25f7cde4adecd00c14b77fe8739e951c/Makefile
Best regards, Andreas