Subject: Re: [alpine-devel] new aport utility: ap
From: Natanael Copa <ncopa@alpinelinux.org>
To: Matt Smith <mcs@darkregion.net>
Cc: alpine-devel@lists.alpinelinux.org
In-Reply-To: <1292358751.171718016@192.168.2.228>
References: <20101213162256.056c0e23@ncopa-desktop.nor.wtbts.net>
	 <1292268414.201528757@192.168.2.228>
	 <20101214083706.2335a220@ncopa-desktop.nor.wtbts.net>
	 <1292358751.171718016@192.168.2.228>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 15 Dec 2010 14:31:27 +0100
Message-ID: <1292419887.26904.30.camel@ncopa-desktop.nor.wtbts.net>
Precedence: list
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On Tue, 2010-12-14 at 14:32 -0600, Matt Smith wrote:
> On Tuesday, December 14, 2010 1:37am, "Natanael Copa" <ncopa@alpinelinux.org> said:
> > On Mon, 13 Dec 2010 13:26:54 -0600 (CST)
> > "Matt Smith" <mcs@darkregion.net> wrote:
> > 
> >> I think having a config file is a great idea.
> > 
> > Maybe /etc/aports/aports.conf
> > 
> > and move /etc/abuild.conf to /etc/aports/abuild.conf ?
> 
> Yeah, that sounds good.
> 
> >> I also have a few ideas that I'd like to see what you think about:
> >> - Rename 'ap' to 'aports'
> > 
> > Will that not cause confusion? When you talk about aports, do you talk
> > about the aports tool or the ported applications, buildscripts?
> 
> Hm.. true, but I'm not sure 'ap' is the best name either.  Depending
> on what all it's intended to do, what about naming it 'aportinfo' or
> some variation of that? Maybe even ainfo.

agree. 'ap' is not really good either.


> >> - Make 'ap' / 'aports' similar to 'apk' in regards to sub-commands;
> >> include abuild, abump, newapkbuild, etc. as sub-commands to 'ap' /
> >> 'aports' (e.g.: aports build -r, aports newapkabuild newpackage)
> > 
> > I was thinking of simplifying the abuild script, remove all the code
> > doing dependencies, recursive building etc, and let 'aports' utility do
> > that, but keep the shell script to do simple building. Like gentoo has
> > 'emerge' and 'ebuild'
> 
> I read the conversation in #alpine-devel regarding this, and it makes
> sense... I'm just not sure what to call the individual tools.
> 
> Perhaps 2-3 tools:
> - abuild / apkbuild / apbuild: build one aport/apk
> - abuild / arec / arbuild: recursive building, etc
> - ainfo: aports information

I need to think more about this. I'll try to focus on the backend libs
for now.

-nc



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---