X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by lists.alpinelinux.org (Postfix) with ESMTP id A1D311EBFF5 for ; Mon, 14 Feb 2011 12:47:39 +0000 (UTC) Received: by bwz12 with SMTP id 12so5222391bwz.13 for ; Mon, 14 Feb 2011 04:47:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=vTLrGgpjku4pNNglWxuRfh6Gn9Qz2qGvB7pDmCdxkSA=; b=TUlv9ciC6OvMU3AIsgDMTRBRiC2khySSBq/OS+livKwA9Acx6uUd50TYivzYYER0hN TeQpaHcZTHvO3qSsoNfpe2ZiZ8K5f1OeVHIsA0lf6rvXnI0HgGqdXjq01pwWXR26BsKz 8xDRDIIlwXhvu1VReTbY+XYB0i3niM8HBLDb4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KJp944IEbnYsWpeXVUfZCzFo9+FN7iJ5pCZLk+c1hQD+8LhfoaLAMCwezS0IMNOFD8 f83hD3+ePTiC/HESCGejuJYxW28nvct/euEjlo88iuwYCEU3z13mfvbCjUt99XaMrW3i keSl9rqsjycnjBuwmQpUqotJZHfGXTFl1HK1o= X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.204.70.134 with SMTP id d6mr3367935bkj.21.1297687657962; Mon, 14 Feb 2011 04:47:37 -0800 (PST) Received: by 10.204.154.143 with HTTP; Mon, 14 Feb 2011 04:47:37 -0800 (PST) In-Reply-To: <50bb473f48ce3aab63e8206ccf85da2d@127.0.0.1> References: <50bb473f48ce3aab63e8206ccf85da2d@127.0.0.1> Date: Mon, 14 Feb 2011 07:47:37 -0500 Message-ID: Subject: Re: [alpine-devel] Alpine package browser From: Jeff Bilyk To: Francesco Cc: Alpine-devel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Francesco, I'd agree that ideally we'd like this in ACF+lua since long-term, that keeps both tools (ACF and package browser) on a common platform. It also would have the advantage, like you say, of having someone else who'd be able to then contribute to ACF, which is good for the long-term (and I'm sure Ted wouldn't mind having the help). That being said, if those who are going to implement this solution (most likely nenolod and clandmeter iirc) prefer another language, like python, then I'm more inclined to say "lets get something out the door", especially something that imho would be a nice feature for the Alpine site. If down the road it could be incorporated into ACF, that'd be great. Just my 0.02$. Jeff On Mon, Feb 14, 2011 at 7:14 AM, Francesco wrote: > On Mon, 14 Feb 2011 12:27:47 +0100, Carlo Landmeter > wrote: >> On Mon, Feb 14, 2011 at 10:58 AM, Francesco Colista >> wrote: > >> If Ted is up to this task to develop this in ACF + Lua then i would >> endorse it. >> This means all new functions/features will also be developed, do we >> want that or should we use existing solutions and focus on development >> of Alpine Linux? > > Dunno if Ted has time to develop this feature, we should ask to him. > I'm just wondering that we should use the actual existing framework and > add features to it. > If someone is available to write lua code for ACF and helps Ted, this > is appreciated. > But, obiouvsly, this is IMHO. > > -- > :: Francesco :: > Jabber: francesco@jabber.org > E-Mail: francesco@bsod.eu > GnuPG: FE9DDD5F > > > --- > Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org > Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org > --- > > --=20 Jeff --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---