Difference: LbSoftUseCases (9 vs. 10)

Revision 102015-11-27 - GerhardRaven

Line: 1 to 1
 
META TOPICPARENT name="LHCbComputing"

Development Use Cases

Line: 44 to 44
  Discussion: I think the general recommendation is to avoid using subtree, submodule and other sub* tools with git (http://blogs.atlassian.com/2014/04/git-project-dependencies/). The real solution is to have a package manager that deals with dependencies between projects/repositories. What we need is an `environment` which contains one or more repositories. In this particular case you would clone the two repositories containing the changes you are interested in testing together (in this case the forks of the HLT and LoKi repositories which contain the proposed changes) and build them. Together they form an `environment`, in which you run what ever things you need to run. --Tim
Added:
>
>
I match your atlassian blog against submodules, and raise you a blog on why subtree is superior: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ On another note: unless we go for a 'one repo per package' model (which I don't like!), a package manager won't solve the problem of adding a single package (which is a small fraction of a repo) to another repo -- but that is the problem that subtree solves, see the item below on "Distributed management of software releases" which demonstrates how to 'split off' a directory from one repo, and subsequently 'add' it to another repo, while keeping the history. The claim is that one can also push back to the original parent repo, but I haven't tried that yet... -- Gerhard
 

Test of the newly developed reconstruction code feects on HLT line under development

Contact: Vava

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback