Ocurrent-wise, it generates the same graph pipeline.
But now instead of failing if a package doesn't install, it still runs the compile step using another sequence of instructions.
It uses an hypothetical voodoo-do --failed command.
Issues: when a package B depends on a failed package A, the compilation of the failure page of B depends on the compilation of the failure page of A, even if there isn't any data dependency. Technically it should be possible to build A and B at the same time but I haven't thought on how to encode that in the ocurrent graph.
Ocurrent-wise, it generates the same graph pipeline. But now instead of failing if a package doesn't install, it still runs the compile step using another sequence of instructions.
It uses an hypothetical
voodoo-do --failedcommand.Issues: when a package B depends on a failed package A, the compilation of the failure page of B depends on the compilation of the failure page of A, even if there isn't any data dependency. Technically it should be possible to build A and B at the same time but I haven't thought on how to encode that in the ocurrent graph.