3

I'm making a simple GUI with Electron for a CLI executable that is distributed under GPLv2. I assume the license isn't an issue since this is a personal project and I'm happy to license mine GPLv2 as well, but I was wondering the correct way to bundle the executable file in my Git source control as it seems like a really bad solution to include it as if it was a source file.

  • Why do you need to distribute the executable? People could compile your code! – Basile Starynkevitch Dec 25 '19 at 6:45
0

If you did not made any modifications to the CLI tool just link to the original repository.

| improve this answer | |
  • 1
    So just to clarify, essentially just add the executable to my .gitignore and cite the original repository on github? – Tman1677 Jul 24 '19 at 20:42
  • If you add executable to .gitignore than you don't distribute it, so you are not even subject to GPL and don't really need to do anything. If you include executable than you distribute and thus required to provide a way to get its source. I think linking to original source is sufficient in this scenario. – rvs Jul 25 '19 at 10:33
  • 1
    @rvs No. If you distribute the executable, the GPL says you must give the "corresponding source" or a written offer to provide the same; i.e. you specifically need to provide the same source of what you used to build that executable. Linking to the project page is not sufficient. – Brandin Jul 27 '19 at 5:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.