Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for "hierarchies of git repositories" as sources of recipes #409

Open
sawenzel opened this issue Jan 12, 2017 · 4 comments
Open
Assignees

Comments

@sawenzel
Copy link

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.

@ktf
Copy link
Member

ktf commented Jan 12, 2017

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:

additional_source:
  "mount_point": "git repository url"

for example we could have:

sources: https://github.com/llvm/llvm
additional_sources:
  "modules/clang": "https://github.com/llvm/clang"

Am I missing anything?

@ktf
Copy link
Member

ktf commented Jan 12, 2017

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.

@sawenzel
Copy link
Author

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?

@ktf
Copy link
Member

ktf commented Jan 12, 2017

We could use the usual syntax:

<repo>@<tag>

to mix match things.

@ktf ktf self-assigned this Feb 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants