X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@lists.alpinelinux.org
Received: from web130107.mail.mud.yahoo.com (web130107.mail.mud.yahoo.com [66.94.238.134])
	by lists.alpinelinux.org (Postfix) with SMTP id 22D281EBFF8
	for <alpine-devel@lists.alpinelinux.org>; Thu, 31 Mar 2011 13:48:21 +0000 (UTC)
Received: (qmail 13988 invoked by uid 60001); 31 Mar 2011 13:48:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1301579301; bh=yF9faBn0Yxtmge09f3GUq8XMRIAxxIOjJ8iIQntyjg4=; 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=wHRrPNlDIa87im1Oub6Qjp0ZHCTDrzjd6KH48ahAaXvRB1bn793CfuTurfclFyrywNh/nD2Gk+w41zoLQuTj4h8MA75+8y/O6tdWuM/uRpIhwTxq/jl8vRUA07Hj8fSd7mExpKtuV5T4gkYki+Webp30d/9IDlkfLXEIRQ3/xr8=
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=eMV79LSwaoetN1/qfL8J0x0bp3Uq5zPZ0r69H7amPgCQNmoeJODtSGmrgFGNzsAg36U5vHd1uBKo5olN6FeCdgQPJgWKwtJ6P7sT1Jlg36IjGSdtV/4i1X1LC1GyIsRt+mFVYao1lcVoB4E+4i9v/PjIN394BxTRHEee/FVwTWM=;
Message-ID: <285851.96584.qm@web130107.mail.mud.yahoo.com>
X-YMail-OSG: 6grxnJEVM1nwa56XyNBKGxXvxm1OXAG3qNB3nw1DviJCj5k
 b33HtUnJWJY5MQ2vYSJfYGpbhmtxw1WaU1xyP8zE5Ff.Clm_TxJScaJ_4LDm
 iZLIIUQIbO_yi.tEFy9lHryJ7QsUfDPazkoLRetSns5oJ2XVPqJkD2SNGwPl
 JFYNQjHDQRAhr6PsPtG8b0FluAtSeWqpFp4eYWh2lso9k5j8ublr4j.tvHSO
 ugklTd7KGzOtX1zqLcUsRfQiekISWq7ElR4yprfWTeZ8QD3zEwbQh5ioP6i6
 64eEEa20M5vraZ9XMqq3.3B3zHICv77GjZTsm1C3a8kngGlGgTyC.hDWzxnr
 FW4kNuBOyjVIRS1sRxRi6s0ct_ofLd7MuCf_wBzfJsBP6GYZjeEaM1OzxwTl
 .wHGXjByt
Received: from [208.74.141.254] by web130107.mail.mud.yahoo.com via HTTP; Thu, 31 Mar 2011 06:48:21 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> <678804.43665.qm@web130120.mail.mud.yahoo.com> <4D948118.8050701@iki.fi>
Date: Thu, 31 Mar 2011 06:48:21 -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: <4D948118.8050701@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

If I have to tag the entire tree for a release, I don't like it.=0A=0AThe r=
eason they were put in separate repos was so that development could be done=
 =0Aindependently. If I have to start doing lots of branching so I can rele=
ase one =0Apackage and continue working on another, I don't think it's wort=
h it.=0A=0ASeparate independent repos for separate independent packages.=0A=
=0ATed=0A=0A=0A=0A----- Original Message ----=0AFrom: Timo Ter=E4s <timo.te=
ras@iki.fi>=0ATo: Ted Trask <ttrask01@yahoo.com>=0ACc: Natanael Copa <ncopa=
@alpinelinux.org>; jeremy@thomersonfamily.com; =0AAlpine-devel <alpine-deve=
l@lists.alpinelinux.org>=0ASent: Thu, March 31, 2011 9:26:48 AM=0ASubject: =
Re: [alpine-devel] Why? ACF - million repos </sarcasm>=0A=0AOn 03/31/2011 0=
4:14 PM, Ted Trask wrote:=0A> 1) Having one ACF git repo would save me some=
 work when updating multiple =0A> packages / releases, but it would add som=
e overhead too. I have a tendency to =0A> have unfinished work (uncommitted=
) on some packages while working on others. =0A> Since git has only one sta=
sh (right?), it would be more difficult for me to =0A> maintain my tree.=0A=
=0AYou can have several of them: man git-stash=0A=0A> 2) Also, building wou=
ld be difficult. What tag would abuild pull? Some packages =0A>=0A> will ha=
ve untagged (not for release) mods that are older than tagged (for =0A> rel=
ease) mods for other packages. Would abuild pull separate tags from the rep=
o =0A>=0A> for each package?=0A=0ABasically you would have single version n=
umber and single tag for the=0Awhole tree. You'd need to bump only that and=
 it'd publish anything=0Achanged in the whole tree.=0A=0AThe per-module ver=
sions would need to be in separate file, and be=0Apreferably automatically =
updated when you modified one of the files for=0Ait. E.g. by git-hook on co=
mmit, or on just before tagging.=0AAlternatively, the submodule package ver=
sion could be just the timestamp=0Ait was last modified.=0A=0A> 3) We shoul=
d avoid breaking the old builds for earlier versions of alpine. =0A>Leave =
=0A>=0A> the old repos, but only use a new, merged repo? I'm a bit gunshy s=
ince the last =0A>=0A> git updates broke all of the aports for packages hos=
ted on git.a.o.=0A> =0A> So, I'm ok with moving to one git repo, but it sou=
nds like quite a complication =0A>=0A> for abuild. And, I'm not going to be=
 the one that has to implement it.=0A=0AYes, it'd be new feature of abuild.=
 And probably needs some thought if=0Ait's to be done.=0A=0AThis was just w=
ish world I had. But obviously ncopa would have to do=0Awacky stuff in abui=
ld to make this work.=0A=0A- Timo=0A


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