From: Bryan Gardiner <bog@khumba.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] On ebuild files owership
Date: Thu, 30 Jan 2025 20:24:12 -0800 [thread overview]
Message-ID: <20250130202412.4c99eb87@kyouma> (raw)
In-Reply-To: <1738251858.69292191@f166.i.mail.ru>
On Thu, 30 Jan 2025 18:44:18 +0300
Alexander Kurakin <kuraga333@mail.ru> wrote:
> > 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 misspoke a bit with my "because" above, I leave it as two lines for
two separate entities; that's what feels most readable to me. For
example:
# Copyright 1999-2021 Gentoo Authors
# Copyright 2023 Bryan Gardiner <bog@khumba.net>
# Distributed under the terms of the GNU General Public License v2
> > 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?
Yes that's true, this doesn't apply in our case. Just wanted to
provide some more detail about Gentoo's policies.
Cheers,
Bryan
next prev parent reply other threads:[~2025-01-31 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 15:44 [gentoo-user] Re: [gentoo-user] On ebuild files owership Alexander Kurakin
2025-01-31 4:24 ` Bryan Gardiner [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-28 13:34 Alexander Kurakin
2025-01-30 6:31 ` 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=20250130202412.4c99eb87@kyouma \
--to=bog@khumba.net \
--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