Date: Fri, 1 Sep 2017 20:36:28 +0100
From: =?iso-8859-1?B?Q+Fn?= <ca6c@bitmessage.ch>
To: alpine-devel@lists.alpinelinux.org
Subject: [alpine-devel] Alpine ports layout
Message-ID: <20170901193628.GB31533@alpine.my.domain>
References: <1498870383-12828-1-git-send-email-assafgordon@gmail.com>
 <20170829085033.6002c914@vostro.util.wtbts.net>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20170829085033.6002c914@vostro.util.wtbts.net>
User-Agent: Mutt/1.8.3 (2017-05-23)

Timo Teras wrote:

> New aports should start in 'testing'. We don't usually accept direct
> contributions to 'main' or 'community'. In most cases 'community' will
> be the right place for package, and I suspect this will be datamash's
> place when matured. Packages in 'main' are expected to have long
> maintained stable release branches.

I think that these conditions are vague. When should a testing port
become a community one and a community one become main?

How about splitting ports into categories, so gcc would be lang/gcc,
vim would be editors/vim and firefox would be www/firefox? Those that
aren't stable could land in wip, like in pkgsrc.

--=20
ca=F3c



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---