X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@lists.alpinelinux.org
Received: from web130120.mail.mud.yahoo.com (web130120.mail.mud.yahoo.com [66.94.239.40])
	by lists.alpinelinux.org (Postfix) with SMTP id 20F211EBFF8
	for <alpine-devel@lists.alpinelinux.org>; Thu, 31 Mar 2011 13:14:08 +0000 (UTC)
Received: (qmail 52525 invoked by uid 60001); 31 Mar 2011 13:14:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1301577247; bh=o3TTD4mERsz+SmciYfqB8z1rmjIUOubjSUKMtbExf7A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=eIXhRWvPy0Vm0pGThug+Va5bbBsMkID0j8vRMACYctNCnb/fCOXWMfj4yXJQyycrkJlRoc+DX95Q0QX5kxJ+hJt/ABcG5xdy6jKmCyzEYLUwjDEzOZjZcvxqxPQeVH+VGBWoIvABYXDl0gKCXLbZ4fbyG6a7P7zZZWjPzNdMeE4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=EkfWQnpdZ07wO/tVb2GTRcvhgzGjKVtzSJsBbyl/8dD6qRP3zTb7u1jFx+iQmEHDmA5e4QBQ7GxO7pbW/JLezQTd3ZxYqACp958JKTpvEKZApFBy7E4ycm310y2CMydKRT2ZcWd6l4Aj2Cm+jJWJfu0CxTxYKQbXP2VqVkgHJVk=;
Message-ID: <678804.43665.qm@web130120.mail.mud.yahoo.com>
X-YMail-OSG: Vrk6Mb8VM1l7SCezEN41qW8fooM1tW_lrz69NCeUCUGkxSZ
 zAbB8Or8M1Q1T6oOX1g0G_wFd9ueCQsF1YpzuVZROd7I3rLdJBPOa9cF.poc
 c6l_Ib.dw8tStwbBT5QEJyc7TMtGYqSj_yosXPgkVb3YlqxQVfBniqm86Atx
 LvdoQUpLuYul4lWXNz2vOyceM.XZ5Y9z3jAbPgB0u2rFFGFS8Wlye0IMxpo6
 1Bn6THNODfH21Zg3O2yTPwoWzRpKHKG.5auX47yvyCHY9dFq8Um85IoVywPt
 d_3_VOLMUMsOEEGG5PC1jOSJDl9wspRfCEndAw.gHZTcCRlr7S6P4U_orpov
 .1soyqpN5Dr.jY_CFBDl5364B_flBIg8uWzS2.j45ECCs6uS9ow.TUDI7FRo
 K6du76.nA
Received: from [208.74.141.254] by web130120.mail.mud.yahoo.com via HTTP; Thu, 31 Mar 2011 06:14:07 PDT
X-Mailer: YahooMailRC/559 YahooMailWebService/0.8.109.295617
References: <AANLkTindJPfApS9KrK_a2sJ4BxwDEk6+54b4zLAr=wJb@mail.gmail.com> <20110331141803.67f714de@ncopa-desktop.nor.wtbts.net> <899171.33677.qm@web130121.mail.mud.yahoo.com> <4D94795D.7040206@iki.fi>
Date: Thu, 31 Mar 2011 06:14:07 -0700 (PDT)
From: Ted Trask <ttrask01@yahoo.com>
Subject: Re: [alpine-devel] Why? ACF - million repos </sarcasm>
To: =?iso-8859-1?Q?Timo_Ter=E4s?= <timo.teras@iki.fi>
Cc: Natanael Copa <ncopa@alpinelinux.org>, jeremy@thomersonfamily.com,
  Alpine-devel <alpine-devel@lists.alpinelinux.org>
In-Reply-To: <4D94795D.7040206@iki.fi>
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

1) Having one ACF git repo would save me some work when updating multiple =
=0Apackages / releases, but it would add some overhead too. I have a tenden=
cy to =0Ahave unfinished work (uncommitted) on some packages while working =
on others. =0ASince git has only one stash (right?), it would be more diffi=
cult for me to =0Amaintain my tree.=0A=0A2) Also, building would be difficu=
lt. What tag would abuild pull? Some packages =0Awill have untagged (not fo=
r release) mods that are older than tagged (for =0Arelease) mods for other =
packages. Would abuild pull separate tags from the repo =0Afor each package=
?=0A=0A3) We should avoid breaking the old builds for earlier versions of a=
lpine. Leave =0Athe old repos, but only use a new, merged repo? I'm a bit g=
unshy since the last =0Agit updates broke all of the aports for packages ho=
sted on git.a.o.=0A=0ASo, I'm ok with moving to one git repo, but it sounds=
 like quite a complication =0Afor abuild. And, I'm not going to be the one =
that has to implement it.=0A=0ATed=0A=0A=0A=0A----- Original Message ----=
=0AFrom: Timo Ter=E4s <timo.teras@iki.fi>=0ATo: Ted Trask <ttrask01@yahoo.c=
om>=0ACc: Natanael Copa <ncopa@alpinelinux.org>; jeremy@thomersonfamily.com=
; =0AAlpine-devel <alpine-devel@lists.alpinelinux.org>=0ASent: Thu, March 3=
1, 2011 8:53:49 AM=0ASubject: Re: [alpine-devel] Why? ACF - million repos <=
/sarcasm>=0A=0AOn 03/31/2011 03:48 PM, Ted Trask wrote:=0A> Yes, the reason=
 there are lots of repositories is for ease of releasing =0A> packages. Whe=
n they're separate, they can be released separately with different =0A>=0A>=
 versions. It can be annoying when I need to update a bunch of packages at =
the =0A> same time, like I did yesterday. But, that's pretty rare. Usually =
when I make a =0A>=0A> major rev bump on core and have to update all affect=
ed ACFs.=0A=0AI really dislike the multiple acf repos too.=0A=0AWould it be=
 possible to instead have abuild do subpackage version based=0Aon the sourc=
es? That we would not have the downsides ncopa mentioned=0Aearlier.=0A=0ATh=
is would also ease the tagging, cloning and setting up of non .apk=0Abased =
acf tree. Because now you have to do multiple checkouts and create=0Amultip=
le links to make the thing work from git checkout.=0A=0AMy vote would be to=
 improve abuild to have version number override on=0Aper-subpackage basis. =
That way single tag of main acf.git would=0Aautomatically re-build the upda=
ted source packages.=0A=0A- Timo=0A


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---