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

[Benjamin Oldenburg]

As you know, I am creating a script (*ixes) to simplify the process.

I have had a busy week but I will take care of finishing it now.

Regards,

Ben




-----Original Message-----
From: Kevin P. Fleming <kpfleming at digium.com>
Reply-to: Asterisk SCF Steering Committee discussions
<asterisk-scf-committee at lists.digium.com>
Cc: asterisk-scf-committee at lists.digium.com
Subject: Re: [asterisk-scf-committee] Asterisk SCF 1.0 Feature List, and
progress towards it
Date: Fri, 23 Sep 2011 15:03:28 -0500


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. 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.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-scf-committee/attachments/20110923/3cdd0dad/attachment.htm>