DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        b=k9+GDDXgSyLe6+rvrifl98JEarGVodYYFVon3K5Ll48QyGIRZFbXqHTH3C1T077sBG
         0whaFQgwF8AgLBPwUN3hUiPcmAKVjX73GgGxEQF6upMJ/5OMPu+x0tPVwRVfFeBra4ch
         pSMkHfA1LdRJys4z9qfLSxGfmSPU98jxJ7FUk=
Message-ID: <4CDAA9ED.5040200@gmail.com>
Date: Wed, 10 Nov 2010 08:19:25 -0600
From: Cameron Banta <cbanta@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13pre) Gecko/20101103 Lightning/1.0b2 Shredder/3.1.7pre
Precedence: list
MIME-Version: 1.0
To: Alpine Development <alpine-devel@lists.alpinelinux.org>
CC: Natanael Copa <ncopa@alpinelinux.org>
Subject: Re: [alpine-devel] Alpine 2.2
References: <1289383750.18266.23.camel@ncopa-desktop.nor.wtbts.net>
In-Reply-To: <1289383750.18266.23.camel@ncopa-desktop.nor.wtbts.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 11/10/2010 04:09 AM, Natanael Copa wrote:
> Hi,
>
> So Alpine 2.1 is out and its time to start plan for alpine-2.2. Here are
> some of the things I would like to do for the 2.2 release, scheduled to
> May 2011.
>
> * x86_64 alpine port
> * java support (openjdk)
> * Go Lang support
> * llvm/clang support (maybe we can base alpine-3 completely on clang)
> * improve admin tools, setup-alpine, ACF, unattended installer etc
> * apk-tools: "install_if" (or "conditional groups")
> * lua binding to apk-tools
> * improve abuild (move dependency handling to lua code, build in empty
> chroot)
> * support for cross compiling in abuild?
> * autobuilding of edge snapshot iso images
> * improve testing / quality assurance
> * python3?
> * new version of uclibc, linux kernel, and lots of other new apps
> * Qt support
> * GNOME?
>
> Anything else?

Are there any thoughts on whether or not we need a tool to choose 
default versions? For example, if we were to maintain and both Python2.6 
and Python3, it would be nice to be able to choose which one is the 
default.

We could probably port eselect or update-alternatives.

Or, to keep it simple, do we just support one version, or only allow one 
of those packages to be installed at one time?

> If there are some of the above (or something else) you would like to
> work on, please fell free to let me know. I have various of the above
> stuff partially done already.
>
> If you have some ideas please feel free to send feedback. I'm specially
> interested in ideas what we can do to improve the admin tools,
> setup-alpine, setup-disk and quality assurance.
>
> Thanks!
>
> -nc

-Cameron


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---