| Summary: | sys-devel/m4-1.4.17 has dep on autoconf | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Lucian Poston <lucianposton> |
| Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | lucianposton |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=580688 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | ebuild --info | ||
autotools was added for an m4 patch that required a autoreconf. https://github.com/gentoo-mirror/gentoo/commit/d2fb79b419c1da51746a75a5f55e8b10a7993673 https://github.com/gentoo-mirror/gentoo/commit/47fa8d902034cc4c84229830affc623f98e85fdf (In reply to Lucian Poston from comment #0) > Created attachment 431846 [details] > ebuild --info > > Compared the the previous version (1.14.16), m4-1.14.17 has an added build > dependency on autoconf via the autotools eclass. If both m4 and autoconf are > unmerged and pulled in for a merge, it is blocked on the circular dependency. yeah i added that a for bug #580688 suspecting that sys-devel/m4 is part of @system, but its commented out in profiles/base/packages. i'll fix that problem in a different way, thanks for noticing. can you please sync and try again. (In reply to Anthony Basile from comment #3) > can you please sync and try again. Bug appears to be fixed. (In reply to Anthony Basile from comment #2) i don't care too much about the @system status -- m4 cannot depend on autotools. the ebuild even has a comment for a long time now: # remember: cannot dep on autoconf since it needs us we might need to duplicate that above the inherit line to keep this from happening again. (In reply to SpanKY from comment #5) > (In reply to Anthony Basile from comment #2) > > i don't care too much about the @system status -- m4 cannot depend on > autotools. the ebuild even has a comment for a long time now: > # remember: cannot dep on autoconf since it needs us > > we might need to duplicate that above the inherit line to keep this from > happening again. i tested for a circular dep by doing a catalyst run and didn't hit it. so if there's no problem during a catalyst run and m4 is in @system, why aren't we okay? i get that autotools calls m4 etc, but we have lots of packages like that in @system. (In reply to SpanKY from comment #5) > (In reply to Anthony Basile from comment #2) > > we might need to duplicate that above the inherit line to keep this from > happening again. Instead of comments, consider programatically checking whether autoconf is in DEPEND. |
Created attachment 431846 [details] ebuild --info Compared the the previous version (1.14.16), m4-1.14.17 has an added build dependency on autoconf via the autotools eclass. If both m4 and autoconf are unmerged and pulled in for a merge, it is blocked on the circular dependency.