From: "Alexander Kurakin" <kuraga333@mail.ru>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: [gentoo-user] On ebuild files owership
Date: Thu, 30 Jan 2025 18:44:18 +0300 [thread overview]
Message-ID: <1738251858.69292191@f166.i.mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
> Hi Alexander,
>
> My two cents as a third-party overlay maintainer.
Hi Bryan,
thanks for the reply!
> That is what I do. I preserve any existing copyright statement when I
> import an ebuild from elsewhere, and I add a copyright line for myself
> too once I've made significant changes. Those are two separate
> copyright statements, because the years in the Gentoo line are almost
> always not the same as the years I've modified the file. And for my
> own ebuilds I only have a copyright line for myself.
Understood, thanks! Yes,
> <copyright> := <statement>[, <statement>, ...]
> <statement> := <date> <author(s)>
so you/we have one line but two statements in the copyright :)
>
> I think the simplified attribution with "Gentoo Authors" can make it
> hard to find the original authors of ebuilds once they've been copied
> between repositories, because it requires digging to find which
> repository it came from (hopefully that was recorded somewhere),
> pulling that repo down (gentoo.git is big), then looking up the
> authors there. So that's why I personally bother to use a separate
> copyright line.
Totally agree!
>
> Also, have you seen GLEP 76, the official Gentoo copyright policy? It
> goes over this topic:
>
> https://www.gentoo.org/glep/glep-0076.html
>
Yes, thanks, but
> This GLEP introduces a copyright and licensing policy for Gentoo projects.
We’re taking about ebuilds outside of the Gentoo projects, aren’t we?
> Cheers,
> Bryan
>
Sincerely,
Alexander Kurakin.
[-- Attachment #2: Type: text/html, Size: 2481 bytes --]
next reply other threads:[~2025-01-30 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 15:44 Alexander Kurakin [this message]
2025-01-31 4:24 ` [gentoo-user] On ebuild files owership Bryan Gardiner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1738251858.69292191@f166.i.mail.ru \
--to=kuraga333@mail.ru \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox