From: Zac Medico <zmedico@gentoo.org>
To: Zac Medico <zmedico@gentoo.org>, Ulrich Mueller <ulm@gentoo.org>,
gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH 2/2] Update /usr/portage references (bug 378603)
Date: Sun, 5 Aug 2018 23:03:42 -0700 [thread overview]
Message-ID: <2d5034e7-e3c6-4a33-7cec-45397d7a953a@gentoo.org> (raw)
In-Reply-To: <a9bd66d6-cb14-4e04-7227-7267eb12f829@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1148 bytes --]
On 08/05/2018 10:46 PM, Zac Medico wrote:
>>> --- a/lib/portage/cache/flat_hash.py
>>> +++ b/lib/portage/cache/flat_hash.py
>>> @@ -144,7 +144,7 @@ class database(fs_template.FsBased):
>>> # Only recurse 1 deep, in order to avoid iteration over
>>> # entries from another nested cache instance. This can
>>> # happen if the user nests an overlay inside
>>> - # /usr/portage/local as in bug #302764.
>>> + # /var/db/repos/gentoo/local as in bug #302764.
>>
>> Shouldn't a local overlay be in /var/db/repos/local, but never inside
>> of the gentoo repo?
>
> Yes, but for a long time /usr/local/portage was somewhat standard, in
> fact it's still mentioned here:
>
> https://wiki.gentoo.org/wiki/Custom_repository
>
> Nowadays, repository verification will prevent that from working...
Actually the wiki has /usr/local/portage, but the default rsync options
have has --exclude=/local for a very long time. It might be safe to
remove it, but I guess it's probably safest to trigger a warning message
first, since some people might still be using it with rsync-verify disabled.
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-08-06 6:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 0:23 [gentoo-portage-dev] [PATCH 0/2] Change /usr/portage council approved locations (bug 378603) Zac Medico
2018-08-06 0:23 ` [gentoo-portage-dev] [PATCH 1/2] " 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 [this message]
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=2d5034e7-e3c6-4a33-7cec-45397d7a953a@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
--cc=ulm@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