X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by lists.alpinelinux.org (Postfix) with ESMTP id 153D61EBFF5 for ; Mon, 14 Feb 2011 13:51:42 +0000 (UTC) Received: by iyb26 with SMTP id 26so4864355iyb.13 for ; Mon, 14 Feb 2011 05:51:41 -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=Tur8beUlpXuMK334AO061V3iSodRA+m7qqd5XADGhg4=; b=XIp1TxHgovVfB5ykNYaIJ7CrTESSWFepkVvsSgnS37L2AzAINjHRANX1LTXyMKYNNE Y4IfJIhnm4dSLuUUidlzQtWm/zUOTkKt8gFZQ/jICqtA//89Vj9x745wquLa6foxVMIa OJXxB7aQoCOyt9CqCS6WcOmUFkpnaCppX2+MM= 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=t8kg9a7pFNpLX+CC+8YPLXZbkxj5cu/OJKa35askpTIpmVhQfjc4oGjeDNZdHSxXVM NJe/h2DyLIinnS1krXr76IQOgfLADFCuOHWNvJNyc/S18sKnC+GhAzgTlQYMQIN5RJiB Q+YQjhr9f7egCH1E+MsWFlaUQTWpsfRhGOGnI= 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.231.33.195 with SMTP id i3mr2937532ibd.161.1297691501722; Mon, 14 Feb 2011 05:51:41 -0800 (PST) Received: by 10.231.19.12 with HTTP; Mon, 14 Feb 2011 05:51:41 -0800 (PST) In-Reply-To: <5ec01bd4fa4e0e999c4481d0b9d3b602@127.0.0.1> References: <50bb473f48ce3aab63e8206ccf85da2d@127.0.0.1> <5ec01bd4fa4e0e999c4481d0b9d3b602@127.0.0.1> Date: Mon, 14 Feb 2011 14:51:41 +0100 Message-ID: Subject: Re: [alpine-devel] Alpine package browser From: Carlo Landmeter To: Francesco Cc: Jeff Bilyk , Alpine-devel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Mon, Feb 14, 2011 at 1:55 PM, Francesco wrote: > On Mon, 14 Feb 2011 07:47:37 -0500, Jeff Bilyk > wrote: >> 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. =A0It >> 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). =A0That >> 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. =A0If down the road it could be incorporated into ACF, >> that'd be great. =A0Just my 0.02$. >> > > From this point of view, sound reasonable. > The idea is good, and the alpine website does not use ACF. > I'm not referring, infact, to alpine website, but for our backend. > For public website, agree at 100%. This backend should be some sort of apk overlay to which we can add for instance maintainer and contributor. Because apk-tools is developed as a general package manager (not necessarily Alpine Linux) I think the apk index has some restrictions. It would be really nice if we can sort on maintainer/contributor and quickly check which packages belongs to you. Also allowing to flag packages as out of date and update maintainer/contributor would be a nice addition. Of course there are many more features we can add, but for me this is a prio. --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---