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
Cc: Zac Medico <zmedico@gentoo.org>
Subject: [gentoo-portage-dev] [PATCH 0/2] Change /usr/portage council approved locations (bug 378603)
Date: Sun,  5 Aug 2018 17:23:45 -0700	[thread overview]
Message-ID: <20180806002347.18237-1-zmedico@gentoo.org> (raw)

This includes a _compat_upgrade.default_locations script that the
ebuild can call in pkg_preinst in order to maintain backward-compatible
defaults when appropriate. The new defaults are specified in the
summary of the 20180729 council meeting:

Vote: Default locations for the Gentoo repository, distfiles, and
binary packages will be, respectively:
   /var/db/repos/gentoo
   /var/cache/distfiles
   /var/cache/binpkgs
Accepted with 6 yes votes and 1 no vote.

See: https://projects.gentoo.org/council/meeting-logs/20180729-summary.txt
Bug: https://bugs.gentoo.org/378603

Zac Medico (2):
  Change /usr/portage council approved locations (bug 378603)
  Update /usr/portage references (bug 378603)

 cnf/make.conf.example                            | 12 ++--
 cnf/make.globals                                 |  4 +-
 cnf/repos.conf                                   |  2 +-
 lib/portage/__init__.py                          |  2 +-
 lib/portage/_compat_upgrade/__init__.py          |  0
 lib/portage/_compat_upgrade/default_locations.py | 82 ++++++++++++++++++++++++
 lib/portage/cache/flat_hash.py                   |  2 +-
 lib/portage/tests/news/test_NewsItem.py          |  2 +-
 lib/portage/tests/resolver/ResolverPlayground.py |  2 +-
 lib/portage/xml/metadata.py                      |  4 +-
 man/ebuild.5                                     |  4 +-
 man/emerge.1                                     |  6 +-
 man/make.conf.5                                  | 20 +++---
 man/portage.5                                    | 26 ++++----
 man/quickpkg.1                                   |  2 +-
 repoman/lib/repoman/__init__.py                  |  2 +-
 repoman/lib/repoman/checks/herds/herdbase.py     |  2 +-
 17 files changed, 128 insertions(+), 46 deletions(-)
 create mode 100644 lib/portage/_compat_upgrade/__init__.py
 create mode 100644 lib/portage/_compat_upgrade/default_locations.py

-- 
2.16.4



             reply	other threads:[~2018-08-06  0:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06  0:23 Zac Medico [this message]
2018-08-06  0:23 ` [gentoo-portage-dev] [PATCH 1/2] Change /usr/portage council approved locations (bug 378603) Zac Medico
2018-08-06  0:23 ` [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references " Zac Medico
2018-08-06  4:59   ` Ulrich Mueller
2018-08-06  5:46     ` Zac Medico
2018-08-06  6:03       ` Zac Medico
2018-08-06  7:30       ` Brian Dolbec
2018-08-06 10:29         ` Ulrich Mueller
2018-08-06 18:35         ` Zac Medico
2018-08-06 21:50           ` M. J. Everitt
2018-08-06 22:39             ` Zac Medico
2018-08-06  5:32   ` [gentoo-portage-dev] [PATCH 2/2 v2] " Zac Medico
2018-08-06  7:44     ` Brian Dolbec
2018-08-06 18:46       ` Zac Medico
2019-04-18 17:03   ` [gentoo-portage-dev] [PATCH 2/2 v3] " Zac Medico
2019-04-18 17:28     ` Ulrich Mueller
2019-04-18 17:54       ` Zac Medico
2019-04-18 17:58   ` [gentoo-portage-dev] [PATCH 2/2 v4] " 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=20180806002347.18237-1-zmedico@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