public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: Zac Medico <zmedico@gentoo.org>, gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: [PATCH 0/2] Add binrepos.conf to support fetchcommand customization (bug 661332)
Date: Sun, 6 Sep 2020 23:52:09 -0700	[thread overview]
Message-ID: <8ebf404c-61d4-9e3c-1ffb-4602e2777fe6@gentoo.org> (raw)
In-Reply-To: <20200907063131.395951-1-zmedico@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1648 bytes --]

On 9/6/20 11:31 PM, Zac Medico wrote:
> Support /etc/portage/binrepos.conf as a replacement for the
> PORTAGE_BINHOST variable. Behavior is similar to repos.conf,
> initially supporting just the sync-uri attribute. Both binrepos.conf
> and PORTAGE_BINHOST can be used simultaneously, in the same way that
> repos.conf and PORTDIR_OVERLAY can be used simultaneously.
> 
> The emerge --info output for binrepos.conf looks like this:
> 
> Binary Repositories:
> 
> example-binhost
> 	sync-uri: https://example.com/packages
> 
> Support customization of fetchcommand and resumecommand in
> binrepos.conf, allowing customized authentication mechanisms for
> each repository.
> 
> Zac Medico (2):
>   Add binrepos.conf to replace PORTAGE_BINHOST (bug 668334)
>   binrepos.conf: support fetchcommand customization (bug 661332)
> 
>  lib/_emerge/BinpkgFetcher.py            |  29 ++++--
>  lib/_emerge/actions.py                  |  13 ++-
>  lib/portage/binrepo/__init__.py         |   0
>  lib/portage/binrepo/config.py           | 131 ++++++++++++++++++++++++
>  lib/portage/const.py                    |   1 +
>  lib/portage/dbapi/bintree.py            |  48 ++++++---
>  lib/portage/tests/emerge/test_simple.py |  14 ++-
>  man/make.conf.5                         |   3 +-
>  man/portage.5                           |  52 ++++++++++
>  9 files changed, 264 insertions(+), 27 deletions(-)
>  create mode 100644 lib/portage/binrepo/__init__.py
>  create mode 100644 lib/portage/binrepo/config.py
> 

I had intended to refer to bug 668302 instead of bug 661332:

https://bugs.gentoo.org/668302
-- 
Thanks,
Zac


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

      parent reply	other threads:[~2020-09-07  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  6:31 [gentoo-portage-dev] [PATCH 0/2] Add binrepos.conf to support fetchcommand customization (bug 661332) Zac Medico
2020-09-07  6:31 ` [gentoo-portage-dev] [PATCH 1/2] Add binrepos.conf to replace PORTAGE_BINHOST (bug 668334) Zac Medico
2020-09-07  6:31 ` [gentoo-portage-dev] [PATCH 2/2] binrepos.conf: support fetchcommand customization (bug 661332) Zac Medico
2020-09-07  6:52 ` Zac Medico [this message]

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=8ebf404c-61d4-9e3c-1ffb-4602e2777fe6@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