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
