| 1 |
On 08/05/2018 10:46 PM, Zac Medico wrote: |
| 2 |
>>> --- a/lib/portage/cache/flat_hash.py |
| 3 |
>>> +++ b/lib/portage/cache/flat_hash.py |
| 4 |
>>> @@ -144,7 +144,7 @@ class database(fs_template.FsBased): |
| 5 |
>>> # Only recurse 1 deep, in order to avoid iteration over |
| 6 |
>>> # entries from another nested cache instance. This can |
| 7 |
>>> # happen if the user nests an overlay inside |
| 8 |
>>> - # /usr/portage/local as in bug #302764. |
| 9 |
>>> + # /var/db/repos/gentoo/local as in bug #302764. |
| 10 |
>> |
| 11 |
>> Shouldn't a local overlay be in /var/db/repos/local, but never inside |
| 12 |
>> of the gentoo repo? |
| 13 |
> |
| 14 |
> Yes, but for a long time /usr/local/portage was somewhat standard, in |
| 15 |
> fact it's still mentioned here: |
| 16 |
> |
| 17 |
> https://wiki.gentoo.org/wiki/Custom_repository |
| 18 |
> |
| 19 |
> Nowadays, repository verification will prevent that from working... |
| 20 |
|
| 21 |
Actually the wiki has /usr/local/portage, but the default rsync options |
| 22 |
have has --exclude=/local for a very long time. It might be safe to |
| 23 |
remove it, but I guess it's probably safest to trigger a warning message |
| 24 |
first, since some people might still be using it with rsync-verify disabled. |
| 25 |
-- |
| 26 |
Thanks, |
| 27 |
Zac |
Archives