From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A9A5E1389E2 for ; Thu, 18 Dec 2014 02:20:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE829E0880; Thu, 18 Dec 2014 02:20:39 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5973FE083E for ; Thu, 18 Dec 2014 02:20:39 +0000 (UTC) Received: from [10.0.31.246] (unknown [100.42.98.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 742ED340619 for ; Thu, 18 Dec 2014 02:20:38 +0000 (UTC) Message-ID: <549239F3.5050702@gentoo.org> Date: Wed, 17 Dec 2014 18:20:35 -0800 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-portage-dev@lists.gentoo.org Subject: Re: [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command References: <5491E7FD.2080203@gentoo.org> <20141217143255.387e52f5.dolsen@gentoo.org> <54921875.9020000@gentoo.org> In-Reply-To: <54921875.9020000@gentoo.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Archives-Salt: 429d854f-f5a8-4c67-b042-e0efb3d4fa39 X-Archives-Hash: 1176bb87f5c00b92b0a74279dfdd210d On 12/17/2014 03:57 PM, Zac Medico wrote: > On 12/17/2014 02:32 PM, Brian Dolbec wrote: >> On Wed, 17 Dec 2014 12:30:53 -0800 > >> But what about the different sync types. How do we handle this in a >> git repo instead of an rsync one? > > I was thinking that we would only need to implement this for the rsync > repo, since that's the only one that includes the glsas. If there's some > reason to implement it for other sync types in the future, then we can > do it when the need arises. Also, at some point we might introduce a notion of submodules, similar to git submodules, and if necessary each submodule could potentially be synced using a different protocol. However, this is way beyond the present needs. For now, simply extending the rsync module to allow syncing of sub-directories should be sufficient (though I would not expose the ability to sync arbitrary directories through the user interface). -- Thanks, Zac