X-Original-To: alpine-devel@lists.alpinelinux.org Received: from luna.geeknet.cz (luna.geeknet.cz [37.205.9.141]) by lists.alpinelinux.org (Postfix) with ESMTP id D0A895C4CB3 for ; Fri, 1 Sep 2017 20:07:09 +0000 (GMT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by luna.geeknet.cz (Postfix) with ESMTPSA id CD15C9FFFB; Fri, 1 Sep 2017 22:07:07 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jirutka.cz; s=mail; t=1504296428; bh=v9TNiMGR/LBW6rurwH7lOinVQcAOJTvdhF7Hu6KJwKI=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=YL6Ixh+LBRD0tU2S7jS32hITjollF9HLN9cYA0DQwBEkPEZDCB+OjyFmiOFfEX4Sk JHv6TItEsjRMCDr9yFlqRB1f7dtpONC/1C/wr+7ebyiOzc2bwLuRfGvndmvZrKnPeM ErygsiMsIXCOSK5j1MjpbF16ZX/0KCeW2MiKl2hY= Content-Type: text/plain; charset=utf-8 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [alpine-devel] Alpine ports layout From: Jakub Jirutka In-Reply-To: <20170901193628.GB31533@alpine.my.domain> Date: Fri, 1 Sep 2017 22:07:07 +0200 Cc: alpine-devel@lists.alpinelinux.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <1498870383-12828-1-git-send-email-assafgordon@gmail.com> <20170829085033.6002c914@vostro.util.wtbts.net> <20170901193628.GB31533@alpine.my.domain> To: =?utf-8?Q?C=C3=A1g?= > How about splitting ports into categories, so gcc would be lang/gcc, = vim would be editors/vim and firefox would be www/firefox? 1. This is orthogonal to main vs. community, i.e. it has totally = different meaning. 2. I know this layout very well from Gentoo. It looked like a good thing = at the beginning, but eventually I found out that it=E2=80=99s really = not. There=E2=80=99s no clear (unambiguous) exclusive relation between = packages and limited set of categories, it=E2=80=99s very common that = one package may fit into multiple categories or none. Jakub > I think that these conditions are vague. When should a testing port > become a community one and a community one become main? > On 1. Sep 2017, at 21:36, C=C3=A1g wrote: >=20 > Timo Teras wrote: >=20 >> 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. >=20 > I think that these conditions are vague. When should a testing port > become a community one and a community one become main? >=20 > 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 > --=20 > ca=C3=B3c >=20 >=20 >=20 > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- >=20 --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---