public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command
Date: Wed, 17 Dec 2014 18:20:35 -0800	[thread overview]
Message-ID: <549239F3.5050702@gentoo.org> (raw)
In-Reply-To: <54921875.9020000@gentoo.org>

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


  reply	other threads:[~2014-12-18  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 20:30 [gentoo-portage-dev] [RFC] Add 'emerge --sync-glsa' action and 'emaint sync-glsa' command Zac Medico
2014-12-17 22:32 ` Brian Dolbec
2014-12-17 22:49   ` Michael Orlitzky
2014-12-17 23:03     ` Brian Dolbec
2014-12-17 23:57   ` Zac Medico
2014-12-18  2:20     ` Zac Medico [this message]
2014-12-19  1:07       ` Zac Medico

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=549239F3.5050702@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox