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=pjKqBCaPUzLYoM6vwpuxZBoGW1+G8MRTfKZWBtgYoVAYHwYaq8rk7oF03RkdPwnt8I
         ReviBTxjIRVsbcTpGrVUR6GnxAD/z/jxOSKXeXHED1csxcsGbX2SN2pLqTmEaTqBCdkZ
         GfSws9WzlXC1mf5NiE9+FTYDSzsPrFoQLEPxY=
Precedence: list
MIME-Version: 1.0
In-Reply-To: <4D5A959B.1090507@nothome.org>
References: <AANLkTimF+B+BFgv3W40mr6hOvSC2-i__JzD08qw1YWw-@mail.gmail.com>
	<4D5A959B.1090507@nothome.org>
Date: Tue, 15 Feb 2011 20:23:17 +0100
Message-ID: <AANLkTi=OUYKckpiZ7h2ia9u5uw8+PYSju8vgG4i3N9q7@mail.gmail.com>
Subject: Re: [alpine-devel] Alpine package browser
From: Carlo Landmeter <clandmeter@gmail.com>
To: Nathan Angelacos <nangel@nothome.org>
Cc: Alpine-devel <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Feb 15, 2011 at 4:02 PM, Nathan Angelacos <nangel@nothome.org> wrot=
e:
> Back to the issue at hand...
>
>> Some topics to discus
>>
>> * Python APKINDEX parser
>
> I *do not* want to start a language war here. =A0But ncopa's leaning towa=
rd
> Lua, and ACF is Lua; Is there a specific reason for python?
>
>> * APKINDEX format (possible to get additional information like
>> maintainer/contributor...)
>> * Parser linking to git/buildbot for updates
>> * APK SQL database schema
>> * Drupal as Package browser (or do we prefer ACF)
>> * APK browser features compared Arch/others
>> * Additional features/information like git rss viewer
>> * ....
>>
>
> I like the concept. =A0Do we start with something that looks like
> http://www.archlinux.org/packages, and go from there?
>
> What's there looks very doable with ACF, even with my skills; but I don't
> want to slow anyone from doing something faster.
>

I have prepared the first part of my drupal module to parse the
apkindex.tar.gz. Drupal's node system is since version 7 very
flexible. In drupal, content is based on a node which belongs to a
particular content type. I will create a specific content type "apk"
which will have all the fields i can parse from apkindex. Then
depending on the repo we can create Taxonomy terms in drupal and link
it so we get a proper structure. We can of course extent the content
type to have more fields like maintainer/contributor or any other
field which is interesting to be browsed. To keep everything
up-to-date I will add an update function which hooks up to drupal cron
so its automatically updated.
When I have something to show I will create a new repo on git.a.o and
push the changes.


>
>
>
>
> ---
> Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org
> Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org
> ---
>
>


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---