Closed AndreyDobrovolskyOdessa closed 3 years ago
This does not sound like a good idea to me.
Thanks for nice and smart redo implementation! Besides intentional removing of .dep files, one or more of them can disappear unintentionally or occasionally. In such a trap i've got caught while playing with redo. And the natural move of fingers is obvious - "redo -f". And!... nothing happens. While the structure of the tree is encoded in the .do files and is sufficient for restore. Many thanks again for beautiful code and kindest regards!
Deleting .dep file of some target makes redo thinking of it as the source. This can be used for blocking some subtree rebuilding. Excluded subtree will be involved into the normal build process after "redo -f".