Date: Tue, 14 Dec 2010 14:32:31 -0600 (CST)
Subject: Re: [alpine-devel] new aport utility: ap
From: "Matt Smith" <mcs@darkregion.net>
To: "Natanael Copa" <ncopa@alpinelinux.org>
Cc: alpine-devel@lists.alpinelinux.org
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Importance: Normal
In-Reply-To: <20101214083706.2335a220@ncopa-desktop.nor.wtbts.net>
References: <20101213162256.056c0e23@ncopa-desktop.nor.wtbts.net> 
 <1292268414.201528757@192.168.2.228> 
 <20101214083706.2335a220@ncopa-desktop.nor.wtbts.net>
Message-ID: <1292358751.171718016@192.168.2.228>

On Tuesday, December 14, 2010 1:37am, "Natanael Copa" <ncopa@alpinelinux.or=
g> said:=0A> On Mon, 13 Dec 2010 13:26:54 -0600 (CST)=0A> "Matt Smith" <mcs=
@darkregion.net> wrote:=0A> =0A>> I think having a config file is a great i=
dea.=0A> =0A> Maybe /etc/aports/aports.conf=0A> =0A> and move /etc/abuild.c=
onf to /etc/aports/abuild.conf ?=0A=0AYeah, that sounds good.=0A=0A>> I als=
o have a few ideas that I'd like to see what you think about:=0A>> - Rename=
 'ap' to 'aports'=0A> =0A> Will that not cause confusion? When you talk abo=
ut aports, do you talk=0A> about the aports tool or the ported applications=
, buildscripts?=0A=0AHm.. true, but I'm not sure 'ap' is the best name eith=
er.  Depending=0Aon what all it's intended to do, what about naming it 'apo=
rtinfo' or=0Asome variation of that? Maybe even ainfo.=0A=0A>> - Make 'ap' =
/ 'aports' similar to 'apk' in regards to sub-commands;=0A>> include abuild=
, abump, newapkbuild, etc. as sub-commands to 'ap' /=0A>> 'aports' (e.g.: a=
ports build -r, aports newapkabuild newpackage)=0A> =0A> I was thinking of =
simplifying the abuild script, remove all the code=0A> doing dependencies, =
recursive building etc, and let 'aports' utility do=0A> that, but keep the =
shell script to do simple building. Like gentoo has=0A> 'emerge' and 'ebuil=
d'=0A=0AI read the conversation in #alpine-devel regarding this, and it mak=
es=0Asense... I'm just not sure what to call the individual tools.=0A=0APer=
haps 2-3 tools:=0A- abuild / apkbuild / apbuild: build one aport/apk=0A- ab=
uild / arec / arbuild: recursive building, etc=0A- ainfo: aports informatio=
n=0A=0A>> - Rename /etc/abuild.conf to /etc/aports.conf and add variable(s)=
 for=0A>> 'ap' / 'aports' pointing to the local aports directory(s)=0A> =0A=
> Hmm... We dont want 2 different tools? One that does the actuall=0A> buil=
ding and one that searches/analyzes the aports tree.=0A=0AAt first I wanted=
 a combined tool, but I don't mind either way.=0A=0A> In any case i think w=
e might want the aports.conf be=0A> readable from shell scripts.=0A=0ASound=
s good.=0A=0A> Thanks for the feedback!=0A> =0A> -nc=0A=0ANo problem.  Let =
me know what you think!=0A=0A- Matt



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---