Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect unconditional RDEPEND-RDEPEND cycles #400

Open
mgorny opened this issue May 30, 2022 · 2 comments · May be fixed by #603
Open

Detect unconditional RDEPEND-RDEPEND cycles #400

mgorny opened this issue May 30, 2022 · 2 comments · May be fixed by #603
Labels

Comments

@mgorny
Copy link
Contributor

mgorny commented May 30, 2022

Unfortunately, since Portage maintainers have historically preferred to add ugly hacks over fixing ebuilds, Portage currently pretends that "pure RDEPEND" cycles aren't there. It would be nice if pkgcheck tries to detect at least unconditional cycles, e.g. A unconditionally RDEP on B, B on C, C on A, and requested developers to use PDEPEND in order to achieve predictable merge order.

@laumann
Copy link
Contributor

laumann commented Jul 25, 2022

CC @laumann

arthurzam added a commit to arthurzam/pkgcheck that referenced this issue Jul 15, 2023
Resolves: pkgcore#400
Signed-off-by: Arthur Zamarin <[email protected]>
@arthurzam arthurzam linked a pull request Jul 15, 2023 that will close this issue
@thesamesam
Copy link
Member

Unfortunately, since Portage maintainers have historically preferred to add ugly hacks over fixing ebuilds, Portage currently pretends that "pure RDEPEND" cycles aren't there.

See also https://bugs.gentoo.org/647824.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants