Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • [bash here is just to exemplify, it could be any other GPL application] that means that, for ex.: as bash is GPL, any bash script (that depends 100% on bash to run), must be released as GPL? also, /bin/bash application is and will continue being a single application on itself that can run independently of myApplication, I did not modify bash to depend on myApplication to run; but.. myApplication, will only be a runnable application if bash is present, that makes bash+myApplication a single application? or just makes myApplication a broken one? because bash could not be present? Commented Dec 15, 2014 at 0:36
  • so in short: by depending on bash to run, myApplication must be GPL too? Commented Dec 15, 2014 at 0:38
  • 1
    "if the two programs are combined so that they become effectively two parts of one program", well, myApplication will do the combining step, making myApplication+bash one application, and so myApplication must be GPL, or am I wrong? Commented Dec 15, 2014 at 0:43
  • In theory, one could write a bash clone under a different license, so it isn't strictly speaking true that bash scripts depend 100% on bash to run. Commented Dec 15, 2014 at 0:46
  • @StevenBurnap, I just found this that says exactly what you said. So, I would be coding in a language, but the interpreter license would not affect the code made in that language, as another equivalent interpreter could have other license. Commented Dec 15, 2014 at 0:53