X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from localhost (3.203.202.84.customer.cdi.no [84.202.203.3])
	(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
	(No client certificate requested)
	(Authenticated sender: nc@alpinelinux.org)
	by mail.alpinelinux.org (Postfix) with ESMTPSA id ED185DC19A2;
	Mon,  5 Mar 2012 21:04:23 +0000 (UTC)
Date: Mon, 5 Mar 2012 22:04:27 +0100
From: Natanael Copa <ncopa@alpinelinux.org>
To: Ted Trask <ttrask01@yahoo.com>
Cc: Jim Pryor <lists+alpine-devel@jimpryor.net>,
 "alpine-devel@lists.alpinelinux.org" <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Understanding alpine-setup
Message-ID: <20120305220427.38088a02@alpinelinux.org>
In-Reply-To: <1330964556.96329.YahooMailNeo@web130102.mail.mud.yahoo.com>
References: <1330852060.31716.140661044540177@webmail.messagingengine.com>
	<20120305094554.23727d3c@ncopa-desktop.nor.wtbts.net>
	<1330941814.16357.140661044929169@webmail.messagingengine.com>
	<20120305152103.08b6b9d8@ncopa-desktop.nor.wtbts.net>
	<1330964556.96329.YahooMailNeo@web130102.mail.mud.yahoo.com>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; i686-pc-linux-gnu)
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, 5 Mar 2012 08:22:36 -0800 (PST)
Ted Trask <ttrask01@yahoo.com> wrote:

> Comments on ACF:
>=20
>=20
> On Monday, March 5, 2012 9:21 AM
> Natanael Copa <ncopa@alpinelinux.org> wrote:
>=20
> >=A0I think it has been mentioned in IRC some time that it would have
> >been
> > nice to integrate the setup-* scripts with ACF better. After all
> > they
> >=A0=A0do partially same job.
>=20
> <snip>
>=20
>=20
> >=A0Also, the idea is also to at some point have a GTK ui for this.
> >Would be nice to use same backend.
>=20
> >=A0=A0I guess this is was what ACF was originally supposed to do but
> >ended up as way too web (and html) centric.
>=20
> >=A0=A0Actually, ACF grew out from "we need to manage Alpine boxes via
> >web and we need to do it *now*". There was a thought that it should
> >be a general purpose configuration framework but ended up as a more
> >or less web only thing.
>=20
> I agree that ACF became too web centric.

It was the time factor that pushed that. We need the web management
fast.

> I'm in the middle of
> significant changes to ACF to make it more generic. So, you should be
> able to use the ACF functionality from a generic Lua application
> and/or from the acf-cli application.

This is one of the motivating factors for wanting move the setup-*
scripts to Lua. Instead of having 2 different frameworks to modify the
config files we have share stuff.

> I've made most of the changes to
> acf-core, but there are corresponding changes needed to EVERY other
> ACF package to be compatible. Considering that I've started a new job
> and am in the process of moving, my ACF development time is minimal
> right now. So, it's extremely doubtful that I will have it done by
> April 1 for Alpine Linux 2.4 as was my goal. We shall see...

Don't stress with it. Take care of your life. If we make it for v2.4, we
make it. Otherwise we take it next release.

Thanks!

>=20
> Ted

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---