Ingmar,
from the most important to the less....
1. Merry Christmas :)
2. Well, i feel myself entrepeneur, at least entrepeneur enough to
mantain an AstLinux package :) Of course help Devels, being only two, i
think as you that this would represent a helping hand, and for me a quite
interesting task.
Thinking carefully, only 1 package seems not to be so much pain (i can be
wrong for what you say). The biggest problem i see is that i think i don't
know enough the AstLinux sources, and when i say that i want to mean how
everyting get chained and works in the compilation process. With some help
of the Devels and others interested i would be pleased to *try* :) mantain
the OSLEC for Zaptel patch. Tests are not a problem as i have analogue line
at home and have an AstLinux mock-up system for personal usage.
Since i came across AstLinux (oh God, thanks! :) i use to work with two
lines of code: trunk and asterisk-beta. I use to work into a vmware system
that i use only for compilation purposes. If this scenario is acceptable for
the Devels in order to comply with the product QA, for me, this is a
challenge i would like to take.
I would like to tell something in this theme also. Surely you don't know
that but i write in the asterisk-es (spanish) mailing list. We have more or
less 1100 members actively working everyday on Asterisk. Some of them are
dCap certified. This is not my case. From talks in this forum appeared
solutions for analogue/digital lines like the polarity inversion and other
important things now in the sources of Asterisk. We have also experienced
members using OSLEC so i think I can have some extra help for this side.
Let's see what the Devels say ;)
Best regards,
Jonathan GF
On Dec 25, 2007 12:23 PM, Ingmar Schraub <[EMAIL PROTECTED]> wrote:
> Jonathan GF wrote:
> > My
> > question was more foocused asking, you that know the sources, if i patch
>
> > the zaptel sources, does this patch pass unnoticed or can cause an error
> > in the compilation?D
>
> A lot of things can go wrong if you patch some code. However, you'll see
> what goes wrong, the compiler doesn't let you stand in the dark and you
> can fix it easily :-)
>
> Why don't you just give it a try?
>
> If it causes an error, fix it.
>
> You can also volunteer to maintain the patch for Astlinux. Help is
> appreciated - especially in this project where there are only two
> developers doing most of the work: Darrick and Kris.
>
> I have done the mISDN stuff for Astlinux. It's often a pain to maintain.
> Why? Because a number of things can go wrong when either we
> upgrade/patch the linux kernel (mISDN uses the kernel sources to
> compile) or there is a new mISDN version available. You give it a try.
> If it applies properly, you are happy & lucky. If it doesn't, you have
> to adjust/fix some patches/.mk files, etc. Don't forget to run some
> tests afterwards.
>
> But it's all doable. So go and get started! :-)
>
> regards and merry christmas,
>
> Ingmar
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Astlinux-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> [EMAIL PROTECTED]
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL
PROTECTED]
