3 ms·

They're saying that if you want to use GPLed code, then you have to follow the GPL rules. Clearly the person writing that code decided to use a GPL license, ins

by asnyder 16y ago

They're saying that if you want to use GPLed code, then you have to follow the GPL rules. Clearly the person writing that code decided to use a GPL license, instead of something more flexible like an MIT or BSD license. Thus it makes perfect sense that they force those that use that code comply with the license chosen. If they didn't, they would be doing a disservice to the code authors. If you don't like the license, don't use code that specifically chose to use that license. There are many alternatives to libraries out there, and as a last resort you can always write your own, original, non-GPLed code that performs a similar function. It's also my understanding that if the situation is such that you wrote the code, then you can change the license on the code you wrote and continue with that base, however, the original code is still GPLed and would remain open. [Updated for clarification]

spot 16y ago
yea but most programs have some libraries. it seems unlikely that one entity will own all the code (unless you happen to be the FSF). unless the libraries are less-than GPL licensed and compatible with the App store terms, then you are stuck. it sounds to me that in many or even most circumstances, the GPL and the App store cannot mix unless Apple makes some allowances. it would be great to hear from the FSF exactly what would be required.
- dedward 16y ago
  As long as the libraries aren't statically linked you are okay there... at least as far as libraries that are part of the stock system goes. (otherwise we'd never be able to build against, say, a differnet libc or anything like that) "However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."

by asnyder 16y ago

spot 16y ago

yea but most programs have some libraries. it seems unlikely that one entity will own all the code (unless you happen to be the FSF). unless the libraries are less-than GPL licensed and compatible with the App store terms, then you are stuck. it sounds to me that in many or even most circumstances, the GPL and the App store cannot mix unless Apple makes some allowances. it would be great to hear from the FSF exactly what would be required.

dedward 16y ago
As long as the libraries aren't statically linked you are okay there... at least as far as libraries that are part of the stock system goes. (otherwise we'd never be able to build against, say, a differnet libc or anything like that) "However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable."