Shon Feder
Shon Feder
There's not a general way of doing that (yet), at least not without fetching the sources, afaik. But that isn't required if `dune tools install ` takes a package name...
There is no incompatibility between installation via command and via config file. Indeed, the former could be implemented via the latter, as you suggest. IMO, it is not clear that...
I wonder if we can ground this more solidly in end-user needs? Because I don't think the way this is heading is very responsive to what, IMO, is the pretty...
> We use `git describe` to find the version so one way might be to tag `3.XX+alpha` on `main` itself, that way `git describe` can find it. Sounds like a...
On some reflection, what I propose is that *after* each release branch is cut for version `l.m.n`, we tag `main` with a snapshot ``l.m.n+1-snapshot`.
> I think that would mean the snapshot tag could contain features that weren't released in l.m.0. Not the end of the world, but is also bound to be confusing...
Just looked at this with @Sudha247 who explained that the current Cmdliner term treats each installable as a subcommand for some reason, constructed here: https://github.com/ocaml/dune/blob/84e0722baf93a763fb82fb3d234ead55e930ab6a/bin/tools/tools_common.ml#L114-L125 We think there should be...
@Alizter are you OK with the state of this? Anything needed for a :heavy_check_mark:
> It would be difficult to change dune's behaviour such that changing the value of %{jobs} doesn't cause targets to be rebuilt, and I think allowing some variables to change...
Assuming we all agree to follow @rgrinberg's advice on sequencing, I'm unassigning @gridbugs, since this can't be worked on yet. > We should wait until we get rid of dune...