d and
parse every ebuild for a given atom, rather than being able to find the
best one just by walking the filenames.
Taahir Ahmed
signature.asc
Description: PGP signature
htly coupled to the state of the tree.
[1]
https://github.com/hasufell/paludis-gentoo-git-config/tree/master/etc/paludis/hooks/sync_all_post
Taahir Ahmed
signature.asc
Description: This is a digitally signed message part.
My apologies for the top-reply.
signature.asc
Description: This is a digitally signed message part.
It seems like a simple before/after comparison of active useflags and the text
of the src_* functions (skipping build and install if they are completely
identical) should catch the majority of unnecessary rebuilds.
On 25 July 2014 13:36 Ian Stakenvicius wrote:
> On 25/07/14 01:15 PM, Andreas K.
d)? Or are these ebuilds correct and cave in the wrong?
It should be noted that the first position (that the dependencies specified in
the ebuilds are not sufficient) is the position of cave's developers. I tend
to agree -- How is cave to know that there hasn't been a brekaing change in a
library's API?
Thanks,
Taahir Ahmed
