It seems to be good if projects using essentially the same code repository (like firefox and a potential geckoview) could share it for build purposes as well. Otherwise they need to clone it separately which seems excessive given the size of, say, mozilla-central.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
I've thought of a couple of ways to solve this, both mainly involve being able to set a custom directory name for git_clones, e.g., repo_name.
One is making this argument available in the "main" section.
Another one is supporting git repositories as inputs, and have the repo_name there.
I think it would be a very interesting idea, because it would help with cases such as Clang and the wasi sysroot (which itself depends on Clang).
In general, it would solve the problem we currently solved by creating projects whose aim is only to package the source code.
I think it would be extremely helpful for the PT use case.
If I understand how RBM works, the solution should not be mutually exclusive, and we could implement both.
Maybe should I open a new ticket for the multiple git inputs?
Also, specifying git repositories as inputs should still support signature verification (with a keyring list specific to the input itself).
@boklm do you think this is feasible? Could we move this to Next?
At the moment PTs break nightly builds.
So, we might want to update their dependencies, and in general it's something that we will likely need to do much more often, since now they're self-updating.
However, I'm opening a couple of tickets in tor-browser-build for that.