public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Luther <SebastianLuther@gmx.de>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] plugin-sync progress report
Date: Sat, 15 Mar 2014 21:48:59 +0100	[thread overview]
Message-ID: <5324BCBB.3040801@gmx.de> (raw)
In-Reply-To: <20140315133210.32f79f55.dolsen@gentoo.org>

Am 15.03.2014 21:32, schrieb Brian Dolbec:
> I've started working on the repository/config.py changes needed for the
> plugin-sync system.
> 
> First:
>   The following class performed checks on the
> repos.conf entries for the sync variables regardless if they were being
> used or not. [...]
> 
> Second:
>   - Should all the repos.conf entires to be synced be validated prior to syncing and fail
>     if there are any errors?
>   - Or, just call each sync module's sync() and let each fail individually 
>     and continue syncing remaining repos?
> 

Maybe that's just me, but I don't like things that sometimes work and
sometimes not. Having some emerge invocations fail with "broken config"
and some not, seems rather ugly to me.

(This also implies that syncing a repo with working config is not
possible as long as there are repos with broken config.)

> Third:
>   - I would like to add a new config item for all repos.
>     It is a variable to define which sources of sync operations which
>     the repo will be allowed to be synced from.  It could be a space separated list
>     which could be used to prevent it from being synced via certain commands.

What exactly does this variable mean? What are emaint or layman doing here?




  reply	other threads:[~2014-03-15 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 20:32 [gentoo-portage-dev] plugin-sync progress report Brian Dolbec
2014-03-15 20:48 ` Sebastian Luther [this message]
2014-03-16  4:31   ` Brian Dolbec
2014-03-15 23:08 ` Alec Warner

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=5324BCBB.3040801@gmx.de \
    --to=sebastianluther@gmx.de \
    --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