1 |
On Thursday 12 Sep 2013 01:28:00 Timur Aydin wrote: |
2 |
> On 09/12/13 01:00, Alan McKinnon wrote: |
3 |
> > Yes of course, it make a great deal of sense now. Basically, your local |
4 |
> > overlay had no idea where the parent portage tree is or how to find it |
5 |
> > so couldn't find the eclass directory. |
6 |
> > |
7 |
> > As I understand it, this information used to be hard-coded magic and |
8 |
> > overlays would "just know where to look". Since recently, you have to |
9 |
> > configure it explicitly and not use hidden super-magic. |
10 |
> > |
11 |
> > You would have been getting confusing messages in emerge output about a |
12 |
> > faulty masters setting for overlays, pity we didn't spot that up front. |
13 |
> > Double pity that there wasn't a clear message or news item about what |
14 |
> > the error meant and the impact.... |
15 |
|
16 |
|
17 |
What happens when you run emerge with the new portage is that this error |
18 |
message pops up: |
19 |
|
20 |
# emerge -uaDv world |
21 |
!!! Repository 'x-portage' is missing masters attribute in |
22 |
'/usr/local/portage/metadata/layout.conf' |
23 |
!!! Set 'masters = gentoo' in this file for future compatibility |
24 |
|
25 |
|
26 |
However, as Alan says it is a puzzle why there wasn't a news item warning |
27 |
users of this new configuration requirement and how things may break if it is |
28 |
not complied with; or why the ebuild does not create itself the |
29 |
'/usr/local/portage/metadata/' directory and populate layout.conf with default |
30 |
values - unless the user has already done so. |
31 |
|
32 |
Either way it shouldn't let the user make WAGs as to what is now necessary for |
33 |
a properly functioning package manager. |
34 |
-- |
35 |
Regards, |
36 |
Mick |