If you are using a library, just add a GPL license to that folder or something like that.
One piece of GPL code in a project tends to make the whole project GPL. I'd recommend keeping it very simple and just put a LICENSE.TXT file at the root of the whole project and append the various licenses together with a mention where each project came from. Updating per-file licenses is a pain in the ass. Best regards, -ben On Wed, May 22, 2013 at 6:36 AM, Stefan Andersson <sander...@gmail.com> wrote: > well I'm adding it to a public bitbucket repo, so I guess I'll have to add > it to each file. > > regards > stefan > > > > > On Wed, May 22, 2013 at 10:52 AM, Raffaele Fragapane > <raffsxsil...@googlemail.com> wrote: >> >> If you're distributing, since you never pay for comments, just add it in >> every file. If you're not distributing just avoid caring altogether :p >> >> >> On Wed, May 22, 2013 at 6:38 PM, Stefan Andersson <sander...@gmail.com> >> wrote: >>> >>> Hello everyone, >>> >>> I was just wondering if anyone has added GPL to their code, and how the >>> practice is. I looked at how they have done in the blender python scripts. >>> So I need to add that block to each file? >>> >>> Anyone experienced in this sort of thing? >>> >>> regards >>> stefan >>> >>> >>> -- >>> Stefan Andersson | Digital Janitor | Generalist for hire >>> blog | showreel | twitter | LinkedIn | Instagram | cell: +46-73-6268850 | >>> skype:sanders3d >>> >>> >> >> >> >> -- >> Our users will know fear and cower before our software! Ship it! Ship it >> and let them flee like the dogs they are! > > > > > -- > Stefan Andersson | Digital Janitor | Generalist for hire > blog | showreel | twitter | LinkedIn | Instagram | cell: +46-73-6268850 | > skype:sanders3d > > -- Best regards, Ben Houston Voice: 613-762-4113 Skype: ben.exocortex Twitter: @exocortexcom http://Exocortex.com - Passionate CG Software Professionals.
