You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I want to be able to create build recipes for situations in which a git repositories are hooked into mother git repositories (this is the case for instance for clang as part of llvm).
This is not supported by alibuild at the moment and currently requires the creation of a custom flat git repository (for llvm + clang) as a workaround.
The text was updated successfully, but these errors were encountered:
Agreed. We should have a way to combine more than one source into one checkout area, with all the goodies which alibuild provides in terms of caching sources and spotting differences to minimise rebuilds. One solution would be to introduce:
One question is how do we expect development packages to work. Will the user have to setup everything by himself? Or maybe this also requires support on alibuild init side.
I think your suggestion should cover the most important (if not all) use cases. And yes, it would be very practical if alibuild init could checkout the complete developing area automatically. We should then probably assume that all of the sub-repositories have the same branch or tag names?
As a user I want to be able to create build recipes for situations in which a git repositories are hooked into mother git repositories (this is the case for instance for clang as part of llvm).
This is not supported by alibuild at the moment and currently requires the creation of a custom flat git repository (for llvm + clang) as a workaround.
The text was updated successfully, but these errors were encountered: