3 | | Another remark: `chicken-do` never orders dependencies or build steps, it only decides whether a build step is to be done or not. The logic in chicken-install should make sure that if the static variant of an extension is built, then .types and .inline files must already exist, as the dynamic variant must have been built before that. The only case where your scenario comes up could be if the types/inline files are removed, but the dynamic extension is not, which would confuse the egg build and would be an intended breaking of the dependency chain. |
| 3 | Another remark: `chicken-do` never orders dependencies or build steps, it only decides whether a build step is to be done or not. The logic in chicken-install should make sure that if the static variant of an extension is built, then .types and .inline files must already exist, as the dynamic variant must have been built before that. The only case where your scenario comes up could be if the types/inline files are removed, but the dynamic extension is not, which would confuse the egg build and would be an intentional breaking of the dependency chain. |