X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 85BD5DC0FAA for ; Mon, 5 Mar 2012 10:03:35 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 74F2420D56 for ; Mon, 5 Mar 2012 05:03:34 -0500 (EST) Received: from web4.nyi.mail.srv.osa ([10.202.2.214]) by compute3.internal (MEProxy); Mon, 05 Mar 2012 05:03:34 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=vZ2lR0Rrowcxa3ZvIVqvmz1IIHU=; b=OfP iLle00U3+yh3Xhym1OFM1nEKfoLB6+jYlyflztFHkDWDle9JKw1KvstPf3BeL7q8 QI38C2QVa5be6F4y7smISrOGv++ednK7ekrUQtSc74man8lke899p49Yk7ueIT9h FOY+BcVmEzrDojm3yLpU9P4yts3HP+bV5De/fCxg= Received: by web4.nyi.mail.srv.osa (Postfix, from userid 99) id 4E10F3C1F53; Mon, 5 Mar 2012 05:03:34 -0500 (EST) Message-Id: <1330941814.16357.140661044929169@webmail.messagingengine.com> X-Sasl-Enc: QyQaU0YbieQDIMl/rPWWEbqhSqnzg2bNV0JID2eqdhzY 1330941814 From: Jim Pryor To: alpine-devel@lists.alpinelinux.org X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Mailer: MessagingEngine.com Webmail Interface In-Reply-To: <20120305094554.23727d3c@ncopa-desktop.nor.wtbts.net> References: <1330852060.31716.140661044540177@webmail.messagingengine.com> <20120305094554.23727d3c@ncopa-desktop.nor.wtbts.net> Subject: Re: [alpine-devel] Understanding alpine-setup Date: Mon, 05 Mar 2012 05:03:34 -0500 > I have been thinking of rewriting the setup-* scripts in lua. There > have been need for unattended installs and better setup-disk script. > There was some unattended patches that i let in but I'm not 100% happy > with that implementation (and have personally neer used it). ... > Anyways... The reason that I haven't put more effort in cleaning up the > setup-* scripts is that I think the long time solution is to make > something in Lua. I just have not had the time to actually implement > it yet. Thanks for your replies Natanael. Can you tell me where to look for any earlier discussion of your dissatisfaction with the current setup scripts? Lua *is* a terrific and small-footprint language to use if something stronger than ash is needed. But to my novice eyes the existing scripts already look like a pretty good system. Maybe needing some tweaks, but also quite flexible. Doesn't the "answerfile" functionality already do this, for instance: > The idea is that you could provide a file with all or parts of the info > and only get prompted of the missing stuff. My main difficulty was the thin documentation, and not having a good overview of how all the pieces fit together. I've now made a variety of small wiki commits to help improve this for others. And the dense new page I already mentioned, . -- Jim Pryor jim@jimpryor.net --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---