I think the problem is that the code will become unreadable.
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.
Chris.
----- Original Message -----
From: "Kim Culhan" <[EMAIL PROTECTED]>
To: "Asterisk on BSD discussion" <[email protected]>
Sent: Sunday, September 25, 2005 2:11 PM
Subject: Re: [Asterisk-bsd] zaptel-bsd
--- Dinesh Nair <[EMAIL PROTECTED]> 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
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
_______________________________________________
Asterisk-BSD mailing list
[email protected]
http://lists.digium.com/mailman/listinfo/asterisk-bsd
