[gentoo-dev] A procedure to move a package from guru to the main tree?

[gentoo-dev] A procedure to move a package from guru to the main tree?

[Andrey Grozin]

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?). What's the correct 
procedure for this? Do I simply commit app-text/ocrmypdf to the tree? Who 
will remove it from guru?

Andrey

Re: [gentoo-dev] A procedure to move a package from guru to the main tree?

[Mike Gilbert]

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.

Re: [gentoo-dev] A procedure to move a package from guru to the main tree?

[Petr Vaněk]

On Mon, Aug 25, 2025 at 11:58:53AM -0400, Mike Gilbert wrote:
> On Mon, Aug 25, 2025 at 8:46 AM Andrey Grozin <grozin@gentoo.org> wrote:
> > What's the correct procedure for this? Do I simply commit
> > app-text/ocrmypdf to the tree? Who will remove it from guru?
> 
> 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.

I think you should do the "move" in ::guru profiles/updates before
introducing the package in ::gentoo.

> Maybe add a soft-blocker on the original package name to your new
> ebuild.

This would not be necessary then.

Petr

Re: [gentoo-dev] A procedure to move a package from guru to the main tree?

[Mike Gilbert]

On Mon, Aug 25, 2025 at 12:19 PM Petr Vaněk <arkamar@gentoo.org> wrote:
>
> On Mon, Aug 25, 2025 at 11:58:53AM -0400, Mike Gilbert wrote:
> > On Mon, Aug 25, 2025 at 8:46 AM Andrey Grozin <grozin@gentoo.org> wrote:
> > > What's the correct procedure for this? Do I simply commit
> > > app-text/ocrmypdf to the tree? Who will remove it from guru?
> >
> > 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.
>
> I think you should do the "move" in ::guru profiles/updates before
> introducing the package in ::gentoo.
>
> > Maybe add a soft-blocker on the original package name to your new
> > ebuild.
>
> This would not be necessary then.

Good idea!

[gentoo-dev] Re: A procedure to move a package from guru to the main tree?

[Anna Vyalkova]

On 2025-08-25, Andrey Grozin 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?). What's the correct 
> procedure for this? Do I simply commit app-text/ocrmypdf to the tree? Who 
> will remove it from guru?
 
Hi!

First, de facto there are multiple maintainers (as you can see in `git 
log`). GURU is a collaborative project.

When you promote a package to ::gentoo, you remove whoever is listed as 
a maintainer in metadata.xml and add yourself. It's considered good form 
to ask the GURU maintainer if they want to join as a proxied maintainer, 
as was said before. You also remove keywords that you haven't tested 
yourself.

Then you remove the package from GURU explaining that it was promoted.  
If you don't remove it, CI job 'duplicates' on GURU will fail and 
complain in #gentoo-guru IRC channel. Someone will notice it and remove 
the duplicate.

Second, I don't think renaming is a good idea. As stated in the Gentoo 
Python Guide[0], package name policy only applies to dev-python/* 
packages. The only reason to change the case is that it can be difficult 
to type so many uppercase letters.

Overall, I think it's good to have OCRmyPDF in ::gentoo, as there would 
be fewer problems with dependencies.

[0]: 
https://projects.gentoo.org/python/guide/package-maintenance.html#package-name-policy

Re: [gentoo-dev] Re: A procedure to move a package from guru to the main tree?

[Mike Gilbert]

On Wed, Aug 27, 2025 at 11:27 AM Anna Vyalkova <cyber+gentoo@sysrq.in> wrote:
> Second, I don't think renaming is a good idea. As stated in the Gentoo
> Python Guide[0], package name policy only applies to dev-python/*
> packages. The only reason to change the case is that it can be difficult
> to type so many uppercase letters.

The Devmanual states that uppercase letters are "strongly discouraged".

https://devmanual.gentoo.org/ebuild-writing/file-format/index.html#file-naming-rules

I take that to mean that we prefer lowercase letters unless there is a
strong reason to use uppercase letters.

Re: [gentoo-dev] Re: A procedure to move a package from guru to the main tree?

[Andrey Grozin]

On Wed, 27 Aug 2025, Anna Vyalkova wrote:
> Second, I don't think renaming is a good idea. As stated in the Gentoo
> Python Guide[0], package name policy only applies to dev-python/*
> packages. The only reason to change the case is that it can be difficult
> to type so many uppercase letters.
The upstream tarball is ocrmypdf-16.10.4.tar.gz; it contains the directory 
ocrmypdf-16.10.4/. I think it is more natural to call the package 
ocrmypdf.

Andrey