<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.3.2">
<TITLE>Re: [asterisk-dev] Solaris zaptel</TITLE>
</HEAD>
<BODY>
Hello,<BR>
<BR>
The Zaptel source code is completely different from the current TRUNK. It would be a large undertaking to ensure the same code base compiled on all platforms. I believe this is why the FreeBSD drivers are separate as well. Basically, Solaris != Linux on multiple levels.<BR>
<BR>
So, for Zaptel, I'd like my own module like: zaptel-solaris/trunk<BR>
<BR>
For Asterisk, I'd like two things. I'd like a branch for Solaris using the stable release branch. This is because the PKGs offered and used should be from the stable branch. Why the branch? Well because it'll take some time to get TRUNK truly able to have Solaris squared away and I need to be able to build packages now. Past dealings with patch submissions for TRUNK have taken a long time to be merged and I really can not wait for those merges to be realized.<BR>
<BR>
I already have a disclaimer on file with Digium.<BR>
<BR>
Thoughts, ideas, or suggestions?<BR>
-Joe<BR>
<BR>
<BR>
On Fri, 2006-07-21 at 10:07 -0700, John Todd wrote:<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<FONT COLOR="#000000">Joe -</FONT><BR>
<FONT COLOR="#000000"> Can you be more specific about what you'd like to see for SVN hosting? The Digium (main Asterisk/Zaptel) SVN server would be an optimal place for this in the asterisk-extras directory, unless your patches can go directly into SVN TRUNK, which would be the ideal method. Of course, you'd need to sign the release and license agreement on http://bugs.digium.com/ (at bottom of page) and send it back to Digium. Can you start a bug in the bugtracker on this? I'm sure that there are many people (including myself) who would be very interested in seeing the Solaris Zap patches make their way into TRUNK.</FONT><BR>
<BR>
<BR>
<FONT COLOR="#000000">JT</FONT><BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>