X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail.wtbts.no (mail.wtbts.no [213.234.126.131]) by lists.alpinelinux.org (Postfix) with ESMTP id A71591EBFF8 for ; Thu, 31 Mar 2011 12:20:14 +0000 (UTC) Received: from localhost (bsna.nor.wtbts.net [127.0.0.1]) by mail.wtbts.no (Postfix) with ESMTP id E59A0AE4002; Thu, 31 Mar 2011 12:20:12 +0000 (UTC) X-Virus-Scanned: Yes Received: from mail.wtbts.no ([127.0.0.1]) by localhost (bsna.nor.wtbts.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JOt32AezfCjB; Thu, 31 Mar 2011 12:20:11 +0000 (UTC) Received: from mail.ytre.org (extmail.nor.wtbts.net [10.65.72.14]) by mail.wtbts.no (Postfix) with ESMTP id 7AC35376250; Thu, 31 Mar 2011 12:20:11 +0000 (UTC) Received: from mail.ytre.org (localhost [127.0.0.1]) by mail.ytre.org (Postfix) with ESMTP id 1339D621BF7F4; Thu, 31 Mar 2011 12:20:11 +0000 (UTC) Received: from ncopa-desktop.nor.wtbts.net (unknown [10.65.65.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ncopa@ytre.org) by mail.ytre.org (Postfix) with ESMTPSA id BA0AC621BF7F3; Thu, 31 Mar 2011 12:20:10 +0000 (UTC) Date: Thu, 31 Mar 2011 14:18:03 +0200 From: Natanael Copa To: jeremy@thomersonfamily.com Cc: Alpine-devel Subject: Re: [alpine-devel] Why? ACF - million repos Message-ID: <20110331141803.67f714de@ncopa-desktop.nor.wtbts.net> In-Reply-To: References: X-Mailer: Claws Mail 3.7.8 (GTK+ 2.24.0; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP On Wed, 30 Mar 2011 20:08:31 -0400 Jeremy Thomerson wrote: > Why are all (54) of the ACF modules in their own repo? When those were created there was some expectation that there would be millions of ACF package maintainers. Each acf would be treated as a separate project. There was also a backthought that ACF projects should be distro agnostic and not an alpine linux thing only. > How would > everyone feel about merging them into one repo? Wouldn't that make > it easier to maintain / develop for? We have talked about that before. Then you cannot make new release by just doing git tag. You can ofcourse do a makefile target for releases. We could also treat the ACF as one big monolitic project and have one APKBUILD for it with tons of subpackages. But then would all ACF modules have same version number so there would be 54 package upgrades every time any package changed. I suppose my opinon don't count that much since I'm not involved there so much. I have been thining of looking at ACF when get time but... "get time" tend to never happen. I leave it up to the people who works on it. (tdtrask) > Jeremy Thomerson -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---