[asterisk-dev] Removal of svn:externals in Asterisk branches

Jason Parker jparker at digium.com
Wed Jan 16 11:25:13 CST 2013

On 01/16/2013 11:10 AM, Andrew Latham wrote:
> On Wed, Jan 16, 2013 at 12:05 PM, Jason Parker <jparker at digium.com> wrote:
>> As part of the research towards potentially moving Asterisk to git (If you
>> weren't already aware of this...umm...SURPRISE!), we've come to the conclusion
>> that we can no longer use svn:externals.  Keeping a similar setup would be very
>> difficult to handle, and would provide zero benefit.
>> Asterisk branches currently use two svn:externals : menuselect and mxml
>> (indirectly, through menuselect).  As of Asterisk 1.8 (where asterisk-addons was
>> merged into Asterisk) and DAHDI 2.4 (?), menuselect is used only by Asterisk -
>> this makes the path forward pretty obvious.
>> What we've settled on, at this point, is simply merging menuselect and mxml
>> directly into the Asterisk branches (1.8, 10, 11, and trunk).  In theory, no
>> code will need to change at all.  The changes will be with subversion properties
>> in the merged directories and the way in which changes are merged.  Since they
>> will become a part of Asterisk, the merging would be done in exactly the same
>> manner that Asterisk merges are done today.
>> I'd like to get several things from the folks on this list.
>> 1) A review of the plan.  Why might this be a bad idea?  Any unforeseen issues?
>> 2) A "review" of the branch.  Does it function as expected?  Do any of your
>> scripts now fail?
>> 3) Cookies.
> 1. Can we test this in a user or team branch?
> 2. See number 1
> 3. Its Betsy's birthday, I am sure there are sweets around...

The team branch URL was included in my first email. :)

More information about the asterisk-dev mailing list