Follow-up Comment #13, task #16658 (group administration): [comment #12 comment #12:] >> Copyrightable text files should include copyright and license notices >> themselves. > > Custom additions to the top of these files are not preserved. > > To be clear, the generation of these files is not a one-time initialization > thing.
Then you can generate them so that they be preserved.
> Does that just mean that any GPLv3 code that links to libgit2 needs to
> include an exception to allow that linking?
Quite right.
> If that is the correct understanding, then it's nothing to worry about, since
> my library does not link to Cargo or anything that's only used by Cargo.
You are right, nothing to worry about; however, it's something to understand.
>> Is there a reason why the licenses of those libraries may be ignored?
>
> No, their licenses may not be ignored. They are specified in REUSE.toml.
> Those libraries are not external dependencies, but rather inside of the Rust
> repository. "N/A" is how the cargo-license tool indicates that the "license"
> field is not listed in a library's Cargo.toml file.
Then they need checking in order to understand the licensing terms of the
package in quiestion, needn't they?
> The only thing that gave me uncertainty is that gnu.org lists this license
> under "Free licenses, incompatible with the GNU GPL and FDL". I'm still
> confused about that.
>
> I at least should know whether or not an HTML file may both use the OFL fonts
> and include portions of my GPLed files, because the fonts are for Rust's
> documentation generator.
Typically, using a font to render a text doesn't make a combined work with
that font. Even for the programs that render the text, the font is used as
input data rather than as part of program.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/task/?16658>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
signature.asc
Description: PGP signature
