public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] A procedure to move a package from guru to the main tree?
Date: Mon, 25 Aug 2025 11:58:53 -0400	[thread overview]
Message-ID: <CAJ0EP42zvyrVdk2wWUwL9S+5YBEyzZnHKWao_Ym_9c3bC+0xdg@mail.gmail.com> (raw)
In-Reply-To: <5457578c-203e-129f-b8a1-b53a0749166c@gentoo.org>

On Mon, Aug 25, 2025 at 8:46 AM Andrey Grozin <grozin@gentoo.org> wrote:
>
> Hi *,
>
> I've found an interesting package, app-text/OCRmyPDF, in guru. I've copied
> it to my local overlay, renamed to ocrmypdf, bumped the version 16.10.2 ->
> 16.10.4, removed the patches which were already applied upstream. I'd like
> to add it to the main tree, adding myself as a maintainer (I think I
> should also keep the guru maintainer, right?).

I would ask the GURU maintainer if they wish to co-maintain it by
proxy in ::gentoo.

> What's the correct procedure for this? Do I simply commit app-text/ocrmypdf to the tree? Who will remove it from guru?

I believe all Gentoo devs have write access to the GURU repo, so you
could remove it yourself if you want. Otherwise, I suppose that would
fall to the GURU maintainer and/or the members of the GURU project.

The package rename makes things a little dirty. I'm not sure we really
want to introduce pkgmove entries in ::gentoo for ebuilds that
currently only exist in overlays. Maybe add a soft-blocker on the
original package name to your new ebuild.


  reply	other threads:[~2025-08-25 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-25 12:46 [gentoo-dev] A procedure to move a package from guru to the main tree? Andrey Grozin
2025-08-25 15:58 ` Mike Gilbert [this message]
2025-08-25 16:19   ` Petr Vaněk
2025-08-25 16:58     ` Mike Gilbert
2025-08-27 15:27 ` [gentoo-dev] " Anna Vyalkova
2025-08-27 15:44   ` Mike Gilbert
2025-08-28  4:05   ` Andrey Grozin

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=CAJ0EP42zvyrVdk2wWUwL9S+5YBEyzZnHKWao_Ym_9c3bC+0xdg@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@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