Summary:ASTERISK-20703: Merge menuselect into the Asterisk source
Reporter:Matt Jordan (mjordan)Labels:
Date Opened:2012-11-19 10:54:30.000-0600Date Closed:2014-07-17 14:03:36
Versions:Frequency of
Description:So this ought to be fun.

While discussing the migration process from subversion to git that we'd like to do for the Asterisk project, the issue of menuselect came up.  Namely, that it makes the migration to git a *lot* harder.

Since Asterisk is the only project that uses menuselect, it can be moved into the Asterisk project.  There are a lot of implications to this however, including changes to the repotools project's scripts.  We'll have to also make sure that updating to a version of Asterisk is relatively smooth, as this will have to occur in all of the major version branches.

This will also impact older versions of Asterisk, so the menuselect repo will still have to exist to support versions prior to Asterisk 1.8.
Comments:By: Jason Parker (jparker) 2013-01-18 13:05:53.211-0600

We can't actually do this in subversion.  This will have to wait until we move to git.

By: Shaun Ruffell (sruffell) 2013-01-18 14:27:40.557-0600

Why can't this be done in subversion? Revision DAHDI-Linux [9138|http://svnview.digium.com/svn/dahdi?view=revision&revision=9138] was when the oct612x external was brought directly into the tree in dahdi-linux.  Is it a subversion issue specifically, or related to other scripts / infrastructure that we have built up?

I keep [this commit of menuselect|http://git.asterisk.org/gitweb/?p=team/sruffell/asterisk-working.git;a=patch;h=4c0e78fdd505f4a93fcaa68f00c49518362fd420] floating on my git for-trunk branch.  That patch, plus an edit of svn:externals should be all that is needed?

By: Jason Parker (jparker) 2013-01-18 14:32:56.088-0600

{noformat}$ svn up -r9138
Updating '.':
Skipped 'drivers/dahdi/oct612x' -- An obstructing working copy was found
U   drivers/dahdi
Removed external 'drivers/dahdi/oct612x'
Updated to revision 9138.
Summary of conflicts:
 Skipped paths: 1{noformat}

By: Shaun Ruffell (sruffell) 2013-01-18 14:36:40.318-0600

Ahh...but we don't want to tell people just to either delete the local menuselect then update, or checkout?

By: Jason Parker (jparker) 2013-01-18 14:41:17.797-0600

We decided that it would be too big of a burden on a branch.  Not to mention any scripts that do updates for people, that would fail.

By: Shaun Ruffell (sruffell) 2013-01-18 14:48:34.034-0600

What about then just doing trunk? And leave the branches as-is?

By: Andrew Latham (lathama) 2013-01-18 15:21:59.943-0600

Along with Shaun on this. Do we need the history of menuselect in SVN or can we just add the log?

By: Shaun Ruffell (sruffell) 2014-01-16 22:49:07.888-0600

We discussed this briefly in IRC today.  Perhaps Asterisk 13 will be a good time preparing for an eventual switch to git, starting with getting menuselect into the tree?

By: Shaun Ruffell (sruffell) 2014-01-18 17:02:57.182-0600

This link contains the brief discussion from IRC: http://rikers.org/ibot/%23asterisk-dev/20140116.html.gz

By: Shaun Ruffell (sruffell) 2014-07-14 15:52:39.822-0500

Looks like there is movement here: https://reviewboard.asterisk.org/r/3773/