Le lundi 27 juin 2011 à 20:56 +0200, Jens Lehmann a écrit : > Am 27.06.2011 20:52, schrieb henri GEIST: > > Le lundi 27 juin 2011 à 20:14 +0200, Jens Lehmann a écrit : > >> Am 27.06.2011 18:51, schrieb Junio C Hamano: > >>> One possible working tree organization may look like this: > >>> > >>> -+- lib1 > >>> +- project1/Makefile -- refers to ../lib1 > >>> +- project2/Makefile -- refers to ../lib1 > >> > >> This is what we do at work and it works really well for us. The > >> possible downside (that you can't tie project1 and project2 to a > >> specific version of lib1 in their own repo) is not a real problem > >> in our experience, as the superproject ties the correct combination > >> together. > >> > > > > That is a good starting point. > > I have used this method for some little projects and it work great. > > > > But I had never find a mean to handle the case of project1 depending on > > both lib1 and lib2. > > Hmm, but isn't that covered by having lib1, lib2 & project1 right next > to each other in your superproject? > Sorry I havent read well your schema. I have thought that you reversed dependency and put project1 and project2 inside libs1. Henri GEIST -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html