public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com>
To: Gentoo Portage Development <gentoo-portage-dev@lists.gentoo.org>
Subject: [gentoo-portage-dev] Support for per-repository per-attribute environmental variables
Date: Tue, 9 Dec 2014 01:33:27 +0100	[thread overview]
Message-ID: <201412090133.30218.Arfrever.FTA@gmail.com> (raw)

[-- Attachment #1: Type: Text/Plain, Size: 946 bytes --]

I suggest to add support for per-repository per-attribute environmental variables in Portage.
These variables would be used when PORTAGE_REPOSITORIES is not set.

Example of setting of them by user and detection of them by Portage:

$ env \
> PORTAGE_REPOSITORY:gentoo:location=/var/db/repositories/gentoo-cvs \
> PORTAGE_REPOSITORY:gentoo:sync-type=cvs \
> PORTAGE_REPOSITORY:gentoo:sync-uri=:pserver:anonymous@anoncvs.gentoo.org:/var/cvsroot \
> python -c 'import os, pprint; pprint.pprint([x for x in os.environ.items() if x[0].startswith("PORTAGE_REPOSITORY:")])'
[('PORTAGE_REPOSITORY:gentoo:sync-type', 'cvs'),
 ('PORTAGE_REPOSITORY:gentoo:location', '/var/db/repositories/gentoo-cvs'),
 ('PORTAGE_REPOSITORY:gentoo:sync-uri',
  ':pserver:anonymous@anoncvs.gentoo.org:/var/cvsroot')]

A separator between components of names of these variables cannot be any character valid in names of repositories.

--
Arfrever Frehtes Taifersar Arahesis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-12-09  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-09  0:33 Arfrever Frehtes Taifersar Arahesis [this message]
2014-12-09  8:51 ` [gentoo-portage-dev] Support for per-repository per-attribute environmental variables Alexander Berntsen

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=201412090133.30218.Arfrever.FTA@gmail.com \
    --to=arfrever.fta@gmail.com \
    --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