4 ms·

I thought that the license for B says you can't distribute it along side A. Not that copyright propagates. Obviously, a zip archive containing A and B is a de

by jopsen 3y ago

I thought that the license for B says you can't distribute it along side A. Not that copyright propagates. Obviously, a zip archive containing A and B is a derived work of B. Hence, license of B can say you can't distribute such works. Does distributing A without B make any sense?

im3w1l 3y ago
I have seen stuff like this. Audio programs asking you to specify the location of lame_enc.dll. Emulators asking you to specify location of some bios.
- anthk 3y ago
  The BIOS it's a different case. That's left to the user. Also, the usage of the BIOS happens under emulation, not the main machine. For instance, FUSE with the Sinclair ZX ROM's instead of OpenSE. or Vice with the Commodore BIOSes instead of shipping C64 OpenBIOSes.
quotemstr 3y ago
> I thought that the license for B says you can't distribute it along side A. Nope. The GPL explicitly says > In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.
jameshart 3y ago
> Obviously, a zip archive containing A and B is a derived work of B. It’s not obvious that any copyright attaches to a zip archive at all, any more than hanging two paintings on a wall makes a derived work copyrightable wall. To be a derived work something still has to be a ‘work’. A distribution license can restrict how you are allowed to distribute a work because it can directly restrict your behavior not because it propagates and applies to the container you distribute it in. That is it can just say ‘you can’t distribute this bundled up with other things’, in much the same way as it can say ‘you can’t distribute this without the copyright notice’, or ‘you can’t distribute this on Wednesdays’.

by jopsen 3y ago

im3w1l 3y ago

I have seen stuff like this. Audio programs asking you to specify the location of lame_enc.dll. Emulators asking you to specify location of some bios.

anthk 3y ago
The BIOS it's a different case. That's left to the user. Also, the usage of the BIOS happens under emulation, not the main machine. For instance, FUSE with the Sinclair ZX ROM's instead of OpenSE. or Vice with the Commodore BIOSes instead of shipping C64 OpenBIOSes.

quotemstr 3y ago

> I thought that the license for B says you can't distribute it along side A. Nope. The GPL explicitly says > In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

jameshart 3y ago

> Obviously, a zip archive containing A and B is a derived work of B. It’s not obvious that any copyright attaches to a zip archive at all, any more than hanging two paintings on a wall makes a derived work copyrightable wall. To be a derived work something still has to be a ‘work’. A distribution license can restrict how you are allowed to distribute a work because it can directly restrict your behavior not because it propagates and applies to the container you distribute it in. That is it can just say ‘you can’t distribute this bundled up with other things’, in much the same way as it can say ‘you can’t distribute this without the copyright notice’, or ‘you can’t distribute this on Wednesdays’.