El sáb, 20-10-2012 a las 16:09 +0200, Thomas Sachau escribió: [...] > And finally, as already pointed out by Rich, you should not talk about > any specific EAPI you like/prefer/want to be used everyhwere, but > instead about the issue you want to solve. So just point out the issue > and ask the maintainer to fix it. If he uses a newer EAPI, good. If he > uses another solution, which also fixes the issue, also good. We should > not discuss about a specific way to solve some issues, since this is the > maintainers choice. Our goal should instead be to fix as many issues as > possible with our limited amount of time we have for Gentoo. > >
Also, I see your point, the problem is: - Do we agree we should move to packages with splitted src_configure/prepare phases? In that case eapi >=2 should be enforced. - Do we agree mtimes should be preserved? In that case eapi >=3 should be pushed because all ebuilds will use that enhancement. Regarding other issues like --disable-dependency-tracking, do you know any way to automate a check for knowing if a package that could benefit from it (one using autotools) could pass it or not? If such a check could exist, then, we would be able to only move that packages to newer eapi (or pass option manually) and that would be enough to me. The same would occur with --disable-silent-rules. Please take care I am not trying to get latest eapi used per se, it's because I want to see all new packages using, for example, splitted src_compile phases, or preserved mtimes, or --disable-dependency-tracking being passed on packages that could use it. I thought the easiest way to do that automatically would be to try to always use latest eapi and, then, that packages would be fixed progressively. On the other hand, if you think the other way would be easier, fine, but I wasn't sure how to, for example, check for the --disable-dependency-tracking problem, or check that every package needing revdep-rebuild will be moved to eapi5...
signature.asc
Description: This is a digitally signed message part
