Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 951502 - [Future EAPI] Ban domo
Summary: [Future EAPI] Ban domo
Status: IN_PROGRESS
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: PMS/EAPI (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Package Manager Specification
URL:
Whiteboard: in-eapi-9
Keywords:
Depends on:
Blocks: future-eapi
  Show dependency tree
 
Reported: 2025-03-17 18:00 UTC by Arthur Zamarin
Modified: 2025-06-01 07:23 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Zamarin archtester Gentoo Infrastructure gentoo-dev Security 2025-03-17 18:00:10 UTC
The current actions done by domo are unintuitive, hard to understand, and nearly not used

Used by only 6 packages, 13 ebuilds

Raised in IRC #gentoo-pms
Comment 1 Eli Schwartz gentoo-dev 2025-03-17 18:11:48 UTC
In particular, it's not possible to install for a gettext domain other than ${PN}, which is often not actually what you want (it depends on what the source code declares as the domain) so I simply would not feel safe using it at all.

I'm also skeptical since packages which produce .mo files, rather than only .po files, surely have some buildsystem setup already and I believe it unlikely that they will compile them but not install them. It is comparatively quite common for bad Makefiles to compile an executable or library but not install *them*, so other doXXX helpers seem far more useful.
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2025-05-11 19:31:36 UTC
Approved today unanimously.
Comment 3 Ulrich Müller gentoo-dev 2025-05-13 17:51:53 UTC
In the 2025-05-11 Council meeting, the question arose when and why the domo command was added to Portage. I had briefly mentioned it in my recent post to gentoo-dev:
https://public-inbox.gentoo.org/gentoo-dev/u34f9aqh2@gentoo.org/

There I had also included a link to the commit of portage-1.0 in 2000 which already included the domo command. Here is it again:
https://gitweb.gentoo.org/archive/repo/gentoo-2.git/commit/?id=e1fb2ea89f665be4f89bc7980a8a26cf349d3972
https://gitweb.gentoo.org/archive/repo/gentoo-2.git/tree/sys-apps/portage/files/ebuild?id=e1fb2ea89f665be4f89bc7980a8a26cf349d3972#n824

I couldn't find any archived discussions from that early period about the rationale for adding the command (which isn't surprising).
Comment 4 Larry the Git Cow gentoo-dev 2025-06-01 07:23:00 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/proj/pkgcore/pkgcore.git/commit/?id=fffe9c287c74ed88c4419344e0b7e75a635ebfd2

commit fffe9c287c74ed88c4419344e0b7e75a635ebfd2
Author:     Arthur Zamarin <arthurzam@gentoo.org>
AuthorDate: 2025-06-01 07:15:40 +0000
Commit:     Arthur Zamarin <arthurzam@gentoo.org>
CommitDate: 2025-06-01 07:15:40 +0000

    EAPI=9: ban domo
    
    Bug: https://bugs.gentoo.org/951502
    Signed-off-by: Arthur Zamarin <arthurzam@gentoo.org>

 data/lib/pkgcore/ebd/eapi/9/src_install.bash | 1 +
 1 file changed, 1 insertion(+)