| 1 |
On Tuesday 07 Oct 2014 22:56:28 Mike Gilbert wrote: |
| 2 |
> On Tue, Oct 7, 2014 at 5:48 PM, Mick <michaelkintzios@×××××.com> wrote: |
| 3 |
> > On Tuesday 07 Oct 2014 17:08:11 Neil Bothwick wrote: |
| 4 |
> >> On Tue, 07 Oct 2014 16:39:11 +0100, Peter Humphrey wrote: |
| 5 |
> >> > > Check /etc/portage/repos.conf |
| 6 |
> >> > |
| 7 |
> >> > That's it! Many thanks, Bruce. |
| 8 |
> >> |
| 9 |
> >> Indeed. That directory was either empty or absent on all my systems. |
| 10 |
> >> copying repos.conf from /usr/share/portage and modifying the path got |
| 11 |
> >> rid of the message. |
| 12 |
> > |
| 13 |
> > Shouldn't this file be populated by settings in /etc/portage/make.conf? |
| 14 |
> > |
| 15 |
> > I can't recall editing manually and it seems to have bespoke settings |
| 16 |
> > that I have in make.conf ... |
| 17 |
> |
| 18 |
> Quite the opposite. Ideally, you should remove the PORTDIR setting |
| 19 |
> from make.conf. repos.conf is the newer, more flexible way to |
| 20 |
> configure it. |
| 21 |
> |
| 22 |
> Unfortunately, that will break some of the third-party portage tools |
| 23 |
> which parse make.conf directly. |
| 24 |
|
| 25 |
|
| 26 |
<Scratches head> ... so are we supposed to guess this, wait for a news article |
| 27 |
somewhere, or will it show up in an emerge log somewhere? |
| 28 |
-- |
| 29 |
Regards, |
| 30 |
Mick |
Archives