| Summary: | dev-lang/vala should use virtual/yacc | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Matt Turner <mattst88> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | base-system |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Matt Turner
2012-09-25 05:24:46 UTC
> I question why the vala ebuild author would explicitly list byacc.
Instead of questioning the ebuild author, you could unpack the tarball and read vala's configure.ac:
AC_CHECK_PROGS(YACC, 'bison -y' byacc yacc, :)
if test "$YACC" = :; then
AC_MSG_ERROR([bison not found but required])
fi
I suppose we could switch "|| ( sys-devel/bison dev-util/byacc dev-util/yacc )" to "|| ( virtual/yacc dev-util/byacc )", but I am worried about the possibility of other yacc implementations being added to virtual/yacc, when vala only checks specifically for these three cases.
Don't worry, I've been working with yacc (as a user) and I don't see someone suddenly starting a new yacc project :) On the other hand, bison & all should (and most likely already do, like bison) install a symlink to yacc so the test will succeed here, whatever is installed. + 06 Oct 2012; Pacho Ramos <pacho@gentoo.org> vala-0.10.4-r2.ebuild, + vala-0.12.1-r1.ebuild, vala-0.14.2-r2.ebuild, vala-0.16.1-r2.ebuild, + vala-0.18.0.ebuild: + Move to virtual/yacc, #436168 by Matt Turner. + |