[Asterisk-bsd] The future of 4.X support was [zaptel-bsd]

Alexander Timoshenko gonzo at pbxpress.com
Mon Sep 26 13:17:46 CDT 2005


Chris Stenton wrote:

> I think the problem is that the code will become unreadable.

    yes, you're quite right. zaptel.c has tones of #ifdef's and is hard 
to read even now :(

>
> End of Life for 4.X is scheduled for January 2007 with only critical 
> fixes being available from now until then.
>
> Support for 4.X is expected to dwindle sooner in the ports tree. It is 
> not a requirement for a port to be backwards compatible to be included 
> in the ports tree.
>
> As zaptel/asterisk has never run that well under 4.X my vote would be 
> to drop support for it.

     I don't want to abandone 4.x version completely. And i don't want 
to add ifdefs for the reason you've mentioned before. So
the best solution(IMHO) would be create a separate branch for 4.X.  I've 
browsed CVS history of zaptel.c - and there were no heavy changes
in it for about a year, so tracking changes in this file  and merging 
changes to both branches should not be something extraordinary to do.
As well as using 'svn merge' command should  be easy enough to keep both 
branches synced, for code of wc* drivers will not be affected by
changes in zaptel driver. I'm going to work this way for a some time to 
check whether this process will be as painless as it is supposed to be.

>
> Chris.
>
> ----- Original Message ----- From: "Kim Culhan" <w8hdkim at yahoo.com>
> To: "Asterisk on BSD discussion" <asterisk-bsd at lists.digium.com>
> Sent: Sunday, September 25, 2005 2:11 PM
> Subject: Re: [Asterisk-bsd] zaptel-bsd
>
>
>>
>>
>> --- Dinesh Nair <dinesh at alphaque.com> wrote:
>>
>>> On 09/25/05 02:37 Alexander Timoshenko said the following:
>>> >     Well, i've spent a couple of hours digging into it - it's all
>>> about
>>> > my "beloved" ugly hack called zt_clone. The right way to fix it
>>> is to
>>> > rewrite using dev_stdclone. But it would break 4.X compatibility,
>>> so
>>> > i'm trying to think out the best solution for this right now.
>>>
>>> perhaps ifdefing 6.0 and 4.x functionality separately would help.
>>
>>
>> Many FBSD users would like to help test the zaptel drivers on
>> 6.0-BETA before the final release -more testing time is better :)
>>
>> If its possible to put in some ifdef's to get it running, this
>> would be very helpful.
>>
>> -kim
>>
>> -- 
>> w8hdkim at yahoo.com
>>
>>
>>
>>
>> __________________________________
>> Yahoo! Mail - PC Magazine Editors' Choice 2005
>> http://mail.yahoo.com
>> _______________________________________________
>> Asterisk-BSD mailing list
>> Asterisk-BSD at lists.digium.com
>> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>>
>
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd




More information about the Asterisk-BSD mailing list