new | show | ask | jobs Github

iveqy 3 hours ago

The way I usually solve this is by using git submodules.

▲

bigbuppo 2 hours ago | parent | next [-]

Oh man, I've been laughing at this for 37 minutes straight now.

▲

orthoxerox 2 hours ago | parent [-]

Git submodules are the regular expressions of version control.

	▲	zephen an hour ago \| parent [-]
		When you use regular expressions, you now have two problems. When you use git submodules, you now have five or six problems.

▲

contingencies 2 hours ago | parent | prev [-]

AFAIK the issue with using submodules is you still need the rights to pull the other source repo. However, you can use submodules or LFS to pull a specific build artifact from a build artifact repo or source instead of the source repo, which provides a neat way to manage the dep without fattening the main repo and allows the source repo to be kept separate and high security. I'd certainly do this before changing RCS/VCS solutions. That said, reverse engineering has become relatively trivial in the AI age so the practical utility of providing built rather than source elements is dropping.

	▲	Jare an hour ago \| parent \| next [-]
		You'd have the non-NDA, core stuff in the submodule. The submodule can then be referenced by the big, driving NDA repo. And maybe another repo with a non-NDA, likely simpler "shell" that lets non-NDA devs work with the codebase. If you need to NDA the core stuff instead and thus can't pull it as a submodule, the only thing I can think of is to pull the core as binary/compiled artifacts.
	▲	odo1242 an hour ago \| parent \| prev [-]
		You can set up submodules to not pull the other source repo by default tho