Thanks for the update, Gabriel. Let me check whether this update requires a cvc4 rebuild, and I'll get this going. If you are interested in comaintaining abc, let me know.

I'd be happy to co-maintain abc. I'm co-maintaining yosys, which depends on abc, so that should work out nicely.

Thanks!

I've added you as comaintainer. I only ask that if you update abc, please check whether cvc4 needs a rebuild. Thanks!

Thanks. I've dug around a bit (not familiar with cvc4), so it appears it (cvc4) lists abc-devel as a build dependency. How do you typically determine whether or not a new abc git revision should trigger a cvc4 rebuild? (If this line of inquiry gives you anxiety, please feel free to remove me as an abc co-maintainer :) I'm happy to submit PRs here if yosys upstream decides they want a fresher abc than what's currently available. OTOH, if the cvc4 thing is an easy explanation, happy to stick around and co-maintain abc -- totally your call.

Thanks again,
--G

I run abipkgdiff on the previous and new abc builds, as described at the top of abc.spec. Hmmm, actually those directions are not quite right. I'll commit a fix to them in a moment. Anyway, added functions and variables can be ignored. What I do is look at the list of removed and changed functions and variables, then grep the cvc4 sources to see if any of them are used. If not, no problem. If so, then cvc4 needs a rebuild.

Well, if something cvc4 uses actually gets removed then we'll have to do something more drastic than a rebuild. :-)