Hi Paul,
On Mon, Jan 08, 2024 at 12:54:25PM +0800, Paul Wise wrote:
> On Fri, 2024-01-05 at 22:31 -0800, Ross Vandegrift wrote:
>
> > Imagine I take some code from a freely licensed reference implementation and
> > customize it. The result is a derived work. But this embedding isn't
> >
On Fri, 2024-01-05 at 22:31 -0800, Ross Vandegrift wrote:
> Imagine I take some code from a freely licensed reference implementation and
> customize it. The result is a derived work. But this embedding isn't
> removable - the reference implementation shouldn't accept changes to integrate
> it
Hi Richard,
On Tue, Jan 02, 2024 at 10:31:23PM -0600, Richard Laager wrote:
> I document them the same, except that I also add use the DEP-5 "Comment"
> field to indicate that it came from "B".
That's a nice idea. If I claim my software distribution is licensed under the
GPL, then it's natural
Hi Paul,
On Sat, Jan 06, 2024 at 01:12:50PM +0800, Paul Wise wrote:
> On Mon, 2024-01-01 at 13:16 -0800, Ross Vandegrift wrote:
>
> > Suppose project A includes code from project B.
>
> The best option would be to talk to upstream about removing the copy,
> further advice about embedded copies
On Mon, 2024-01-01 at 13:16 -0800, Ross Vandegrift wrote:
> Suppose project A includes code from project B.
The best option would be to talk to upstream about removing the copy,
further advice about embedded copies is on the wiki:
https://wiki.debian.org/EmbeddedCopies
> How should these files
I document them the same, except that I also add use the DEP-5 "Comment"
field to indicate that it came from "B".
--
Richard
OpenPGP_signature.asc
Description: OpenPGP digital signature
Hello,
Suppose project A includes code from project B. To be good stewards of license
and copyright data, A incorporates B's license and copyright files into their
source distribution.
How should these files appear in d/copyright? I don't see any suggestion in
[1] or [2].
Thanks,
Ross
7 matches
Mail list logo
