On 5/3/07, Junio C Hamano <junkio@xxxxxxx> wrote:
If I were doing this 6 months from now, I would probably use subproject to host the whole tree of other projects somewhere, adjust the build procedure of the primary project to borrow the whole of these other projects not just subtree -- or have appropriate symlinks in the superproject that point into relevant subtrees in the subprojects. If I were doing this today, I would probably use separate repositories, next to the primary project, to host the whole tree of other projects, adjust the build procedure of the primary project to borrow the whole of these other projects not just subtree -- and/or have appropriate symlinks in the primary project that point into relevant subtrees in the neighbouring repositories that host these other projects.
Thank you for your explanations, I'm not sure to truly understand what you propose, (I told you I'm a beginner and not amonq the clever ones!) Do you mean that I have to do the patches I do on the fellow project in the mirror directory, as to keep it as a link? It could be possible when the project is managed by git (with the drawback of adding an extra complexity to dereference the links in the repository when archiving a release, and a lot of problem to export to a public repository) but is not a possibility when the other project is managed by an other scm. I don't understand neither the first solution 'borrow the whole project'. To better explain the problem I give a practical case. I'm working to package software for openwrt arm-mipsel system. The whole openwrt buildsystem is available under subversion, it is a big tree (not so huge than the kernel you are accustomed to!) I need in my packages to produce rc scripts and udev conf, hotplug scripts. They depends of the base rc functions of openwrt (int etc), the config system (in lib/config), and the hotplug scripts (/etc/hotplug.d), and I need to patch some of these scripts. I would like to stay in sync with the development of openwrt, the change in the patched files are quite frequent but usualy merge easily. Of course this is only one part of my dependencies, the main tree that is imported in my project is the original package that I modify to tailor it to openwrt. My problem is how to deal with this neither major nor minor dependency. Thanks for taking time to answer. Marc - 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