Opened 9 years ago

Closed 5 years ago

#4057 closed enhancement (fixed)

better GIT/SVN/HG support

Reported by: luigi.mantellini@… Owned by: developers
Priority: normal Milestone: Features Paradise
Component: other Version: Trunk
Keywords: Cc:


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 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,


Attachments (0)

Change History (2)

comment:1 Changed 9 years ago by agb

  • Milestone changed from Kamikaze 8.09 to Kamikaze Features Paradize

Won't make it into 8.09, moving milestone.

comment:2 Changed 5 years ago by florian

  • Resolution set to fixed
  • Status changed from new to closed
  • Version set to Trunk

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.