| Summary: | dev-util/yacc and sys-devel/bison file collision | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Stefano Varesi <stefano.varesi> |
| Component: | [OLD] Development | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | stefano.varesi |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
sys-devel/bison installs the symlink '/usr/bin/yacc -> bison' that collides with '/usr/bin/yacc' installed by dev-util/yacc when FEATURES="collision-protect". This happens in the function pkg_postinst() { if [[ ! -e ${ROOT}/usr/bin/yacc ]] ; then ln -s yacc.bison "${ROOT}"/usr/bin/yacc fi } of sys-devel/bison ebuild. This has also the disadvatage that the symlink doesn't belongs to the sys-devel/bison package and doesn't appear in the output of `equery files sys-devel/bison`. This happens for every version of sys-devel/bison present in portage. I think it should be better to not install the symlink in bison ebuild and put an einfo message to notice that bison can also do the yacc job using '/usr/bin/yacc.bison' or '/usr/bin/bison -y'. Reproducible: Always