[asterisk-scf-committee] Asterisk SCF 1.0 Feature List, and progress towards it

Kevin P. Fleming kpfleming at digium.com
Fri Sep 23 16:22:29 CDT 2011


On 09/23/2011 03:07 PM, Marc Blanchet wrote:
>
> Le 2011-09-23 à 16:03, Kevin P. Fleming a écrit :
>
>> On 09/23/2011 02:59 PM, Marc Blanchet wrote:
>>>
>>> Le 2011-09-23 à 15:43, Kevin P. Fleming a écrit :
>>>
>>>> On 09/08/2011 10:19 PM, Marc Blanchet wrote:
>>>>>
>>>>> Le 2011-09-09 à 11:17, Benjamin Oldenburg a écrit :
>>>>>
>>>>>> Hello Marc,
>>>>>>
>>>>>> I agree about the necessity of a "1-2-3-go" installation procedure and I
>>>>>> have therefore offered to create a tutorial.
>>>>>
>>>>> great, but to me, it is not a tutorial that is need, it is a script that does everything for you.
>>>>
>>>> Well, I'm not sure we want to use a script for that. I think we're going to have two options: a completely documented step-by-step tutorial on the wiki based on building from source, and a set of binary packages for some common Linux distros that let you just install the packages and move on.
>>>>
>>>> The build-from-source method will be preferable for people who want to dive in to the code itself, for everyone else, binary packages would suffice. My concern with scripts is that they can't anticipate every possible thing that could go wrong, and if something does go wrong, the user isn't in a position to try to figure it out because they just 'ran the script'... they don't really understand what it is doing.
>>>
>>> I disagree. I think it should be as simple as ./configure; make; make install. That makes also life much easier to people who take care of ports on multiple distros.
>>
>> Building Asterisk SCF *itself* is that easy; run 'cmake\init-cmake.sh', then 'cmake --build ./build', then 'make -C build install'. The complexity comes into the picture due to the need for a custom version of Ice and Ice plugins, various libraries that distros don't package (or have old broken versions of) and other stuff.
>
> I know. tried it....
>
>> Some of this we can simplify by providing binary packages, but not until we're at a point where things have settled down enough to justify the effort of creating them.
>
> well, I have the opinion that an open-source software should be super easy to install to get some momentum. It is as important as its own core functionality.  I would love to spend some time to do some of the build scripts myself and contribute but I can't at the moment. But my point remains...

No doubt; that's why we're planning to wrap up feature development by 
the end of this month, and then spend all of October whipping the stuff 
we've built into better shape.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org



More information about the asterisk-scf-committee mailing list