[asterisk-scf-committee] Asterisk SCF 1.0 Feature List, and progress towards it
Benjamin Oldenburg
asterisk-scf-dev at bericom.eu
Fri Sep 23 15:46:31 CDT 2011
Well, I think it would at least be a time saver because it practically
does what the How-To suggests.
One way or another, I can't imagine that someone incapable of
understanding what a bash script is doing, will be able to understand
how to even use Asterisk SCF, at least not anytime soon (from what I can
tell).
-----Original Message-----
From: Kevin P. Fleming <kpfleming at digium.com>
Reply-to: Asterisk SCF Steering Committee discussions
<asterisk-scf-committee at lists.digium.com>
To: 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 14:43:04 -0500
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.
More information about the asterisk-scf-committee
mailing list