using https://github.com/onox/orka, I can build orka (which needs orka_types, orka_simd, and orka_transforms), but I cannot build orka_glfw (which depends on orka)
I'm using
path = "file:../orka" in the alire.lock files btw
Alire puts absolute paths in the
alire.lock files
When you say "cannot find C", what does that mean?
orka.gpr:2:06: unknown project file: "orka_simd"
etc.
if I remove orka from orka_glfw and then re-add it with
alr with orka --use=../orka, then alire says:
+⚠ orka_egl ^1.0.0 (new,missing,indirect)
+⚠ orka_simd ^1.0.0 (new,missing,indirect)
+⚠ orka_transforms ^1.0.0 (new,missing,indirect)
+⚠ orka_types ^1.0.0 (new,missing,indirect)Do you want to proceed?
[Y] Yes [N] No (default is No) yes
error: failed precondition from alire-solutions.ads:313
I think using lock files for what you are doing is maybe not the best way.
first, as Fabien said, lockfiles are not intended for manual editing. If you absolutely need to do that, that's something we should fix by adding the necessary functionality elsewhere.
second, having a local index is a solution, but as that is onerous (as you found), a better solution would be needed. The intended approach is to use local pins (for development only, not for publishing). If these fall short, we can see why and how to fix it
so, going back to the original problem, I don't see the full picture. @onox, you described having A -> B -> C. I understand you pinned C from B, and B from A?
As a side note, I'm currently starting work on pins to remote repos. These should allow publishing crates with dependencies on unpublished crates. I guess those also should help with development of several crates at the same time. But local pins should ideally cover all needs, previously.
Finally, for the wider issue of monorepos: IIUC, you mean by that repos where several crates are stored in several folders, the root folder not being itself a crate. These should work normally locally, but there is no provision to publish them as a whole. You can publish them individually, as source files (not as repos, as we lack the option to specify a subfolder with a commit). What you can't currently do (or shouldn't do, as was not in the feature design) is publish local pins to each other. They should refer to themselves in the index. Remote pins (when existing) wouldn't help either in this case as they would also lack the subfolder pointer. Unless we implement that for all repo remotes.
with all that out of the way... I need to get more down to the details with you :) If you'd be so kind @onox to point me to the repo you're working with... Perhaps we can work over this in a new issue at GH.
@mosteo I have 2 monorepos: https://github.com/onox/wayland-ada and https://github.com/onox/orka. I can also publish a very small yarn 2 repo if you want to take a look at that
you mean by that repos where several crates are stored in several folders, the root folder not being itself a crate.
yes
@mosteo See https://github.com/onox/yarn-monorepo <-- only 1 .lock file + 3 package.json files (for 2 packages + 1 for the root)
alr getreplies "No crate requested", as if expecting a crate name as an argument. On Alire 1.0.0
Correct, you have to say alr get <crate> and it will download both the crate and its dependencies