On Wed, 2015-06-17 at 12:25 +0200, Patrick Ohly wrote:
However, there are at least two false positives left in the current code:
* aliases for recipes via PROVIDES
* unnecessarily linking against libs which are not really used
See the TODOs in the code.
Actually, I had written more about
Indirect dependencies occur when a recipe does not declare a depency
on foo because it depends on bar, which in turn depends on
foo. This happens to work, but is fragile and should better be avoided
by listing foo explicitly, because:
* bar might not depend on foo in all configurations
* future
