Hey, The git submodules could be a good choice here. The submodule commit referenced by the container is stored using its commit hash and therefore a submodule does not automatically upgrade. When gem5 is cloned, the --recursive flag must be used in order to clone also all the submodules.
However, every time we add a submodule or we change the referenced commit for a submodule, every collaborator has to make a manual update of his local repository (git submodule update). But maybe we can put this into the git hooks? Regards Matthias Am 03.03.2017 um 21:34 schrieb Andreas Hansson <[email protected] <mailto:[email protected]>>: > Hi Jason, > > How would we keep the external repos in sync? Can a subrepo refer to a > specific version? > > Also note that we need to keep GPL code out of gem5 (including binaries), > not just the source tree, so your bad point (3) below doesn’t change > either way. > > Andreas > > > > On 03/03/2017, 19:35, "gem5-dev on behalf of Jason Lowe-Power" > <[email protected] <mailto:[email protected]> on behalf of > [email protected] <mailto:[email protected]>> wrote: > >> Hi all, >> >> There are a couple of patches in review that add a large chunk of code >> from >> other repositories to gem5 in ext/. Andreas S. has a patch that adds >> PyBind11 and Matthias is updating DRAMPower. And we're thinking about >> including SystemC in a similar way. >> >> Is there a better way for us to include these other projects in gem5's >> source tree? For instance, we could use subrepos. What is the community's >> thoughts on this? >> >> A few things I don't like about including the code in gem5: >> 1) It increases the amount of code in our repository >> 2) It is hard to track updates to these systems >> 3) The code cannot be GPL. >> >> Good thing about including the code in gem5: >> 1) Updates to external code won't break our system >> 2) It's easy to build gem5 without having to download other software >> >> Any other opinions or options for this? >> >> Thanks, >> Jason >> _______________________________________________ >> gem5-dev mailing list >> [email protected] <mailto:[email protected]> >> http://m5sim.org/mailman/listinfo/gem5-dev >> <http://m5sim.org/mailman/listinfo/gem5-dev> > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > _______________________________________________ > gem5-dev mailing list > [email protected] <mailto:[email protected]> > http://m5sim.org/mailman/listinfo/gem5-dev > <http://m5sim.org/mailman/listinfo/gem5-dev> _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
