| 1 |
On Thu, 22 May 2014 15:42:09 +0200 |
| 2 |
"Andreas K. Huettel" <dilfridge@g.o> wrote: |
| 3 |
|
| 4 |
> if you run into issues like this, first try something like |
| 5 |
> |
| 6 |
> emerge -uDNav world |
| 7 |
> |
| 8 |
> (--update --deep --newuse --ask --verbose; note the "deep") |
| 9 |
> (afaik this is the recommended way to update your system anyway) |
| 10 |
> |
| 11 |
> If this doesnt help, you can try giving portage more time to |
| 12 |
> backtrack, add e.g. the following option (warning this may take a |
| 13 |
> while): |
| 14 |
> |
| 15 |
> --backtrack=1000 |
| 16 |
|
| 17 |
Thanks, will do that. |
| 18 |
|
| 19 |
Is there a comprehensive manual about portage and the related tools? |
| 20 |
I mean one which explains how the whole thing works, what are atoms and |
| 21 |
sets and slots and masks; how dependencies work and how the magic USE |
| 22 |
keywords get translated to actual configure parameters, so basically |
| 23 |
the whole logic behind it? Then, with all that basic knowledge how |
| 24 |
emerge et al work on that info and what they actually do? |
| 25 |
|
| 26 |
As a developer probably it's all obvious if not trivial to you, but to |
| 27 |
the uninitiated it looks a bit of black magic. I went to the Wiki and |
| 28 |
went through the handbook, but I couldn't find anything which explained |
| 29 |
the actual concepts and implementation of the whole portage system, |
| 30 |
just practical snippets of actual tool usage rather than the |
| 31 |
foundations. Any pointers to the relevant literature would be most |
| 32 |
appreciated. |
| 33 |
|
| 34 |
Thanks, |
| 35 |
|
| 36 |
Zoltan |
Archives