Hi Boys, I'm still evaluating OpenWRT as The Ultimate Building Environment.
My environment (the arch is not important) is made by a lot of git and svn repositories where my colleagues work every day. [ git1 ] Kernel [ git2 ] Application #1 [ git3 ] Application #2 [ svn1] Application #3 [ git4 ] OpenWRT Each application has a development life with tags, refs, revisions, bugs, resolved bus, etc... When My costumer ask me for a new release (for example #XX) I need to freeze each git tree for each application and create a single build with all contributes from the git/svn trees are well identified This is my real-life scenario. Reading the include/* files I noticed that the svn/git/.... support is still immature. Immature because: - with VERSION is also referenced the REFS on the CVS - with SUBDIR and the FILE are too dependent - every download (for updates) is traduced to "rm -rf THEDIR" and a Clone/checkout... absolutely not efficient. - lack of control on the specific cvs features. - Kernel is considered a "special-case"... no cvs support (using small fixes we cover this problem) I want to understand which are the plans on these point of improvement. I think that using a small effort the cvs support can be improved, becoming usable. my apologies for my opinions... of course, I would like to hear different opinions. Thanks and best regards, ciao luigi -- Luigi Mantellini R&D - Software Industrie Dial Face S.p.A. Via Canzo, 4 20068 Peschiera Borromeo (MI), Italy Tel.: +39 02 5167 2813 Fax: +39 02 5167 2459 Email: [EMAIL PROTECTED]
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
