On 4 June 2015 at 08:46, Andrew Fish <af...@apple.com> wrote: > > On Jun 3, 2015, at 11:33 PM, Ard Biesheuvel <ard.biesheu...@linaro.org> > wrote: > > In any case, I think the consensus is that the EDK2 upstream should > remain a single project if it moves to Git. If anyone disagrees with > this observation but hasn't chimed in yet, please speak up and > motivate your position. > > > Ard, > > I agree with you, but I have to ask the question… How many platform ports in > the single git repro is too much? > > Maybe the answer is it will never be too much? In that case we should have > some tools to help prune the developers repositories. >
To what end exactly? I agree that it may not scale beyond some point in the future, but let's get clear what exactly we want to accomplish by removing source files and folders from the tree that the developer is going to ignore anyway. Disk space? Clutter in the EDK2/ root folder? > If we are going to go with a single git, it seems like the edk2 build system > could “help out”: > 1) Enable more than one package root. Don’t require all the packages to be > in the Root. Allow multiple WORKSPACE paths as starting points. > a) This gives some flexibility, even if it is just adding vendor > directories, or even an edk2 directory for a larger project. Yes, we should make it as easy as possible to build packages and platforms out-of-tree. > 2) Have the log file for the build list all the Packages, or maybe even the > unused packages in the tree for the build. > a) This could enable a tool that pruned out the extra stuff from git that > you don’t need. > b) We could even just emit the script that runs the git commands to adjust > the local repository. > Removing folders containing files that subsequent patches may modify is going to cause conflicts when pulling from the repo, so I guess this may be more cumbersome than you think. So perhaps it is really a matter of adding support to the BuildTools to allow building packages and platforms that exist outside of the EDK2 code and refer to it at build time via a git submodule under EDK2/. Consequently, we should not add any new platforms to the core, and perhaps retire some and move them to a separate platforms tree such as the one Leif has been working on. -- Ard. ------------------------------------------------------------------------------ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
