1 |
2006/3/14, Simon Stelling <blubb@g.o>: |
2 |
> |
3 |
> tvali wrote: |
4 |
> > * Add package to "world" checking all dependencies, but not emerging |
5 |
> > * Remove package from "world" without unmerging |
6 |
> |
7 |
> Uhm, why would you want that? |
8 |
> |
9 |
|
10 |
On my computer, building takes several hours on some packages. I have used |
11 |
it in such way that it builds in several windows on the same time, but i |
12 |
guess that that's not at all the best practice, especially with some |
13 |
combinations of packages. So i would like to add all packages, seeing all |
14 |
blocks and inter dependencies, then start building when ready (and go out of |
15 |
home, when it builds, and be sure that it will do it's best when i'm away). |
16 |
|
17 |
> * Save all important messages into file instead of beeping (i may be away |
18 |
> > from home); optionally replay them at end of update |
19 |
> |
20 |
> elog can do this. |
21 |
|
22 |
|
23 |
Will check out. |
24 |
|
25 |
> * When updating or installing new package, if something goes wrong, still |
26 |
> > emerge other packages, which havent failed packages as dependencies -- |
27 |
> in my |
28 |
> > case, for example, when i do --update, for example, then the fact that |
29 |
> > update of first package fails does not definitely mean that i dont want |
30 |
> to |
31 |
> > update others |
32 |
> |
33 |
> --resume |
34 |
|
35 |
|
36 |
I know --resume, but that's not what i meant. |
37 |
|
38 |
Imagine the situation: |
39 |
emerge -p package1 package2 |
40 |
|
41 |
part1 (needed by package1) |
42 |
part2 (needed by part3) |
43 |
part3 (needed by package2) |
44 |
part4 (needed by package2) |
45 |
part5 (needed by both package1 and package2) |
46 |
package1 |
47 |
package2 |
48 |
|
49 |
now i start "emerge package1 package2" and go to work (or sleep or party or |
50 |
sauna). |
51 |
|
52 |
part2 fails -- some bug or misconfiguration. |
53 |
|
54 |
currently it means that when i came back home, i see that part1 is built, |
55 |
but nothing more and 4-5 hours are actually just wasted. |
56 |
|
57 |
There should be a way to have all those built when i came home: |
58 |
|
59 |
part1 (needed by package1) |
60 |
part4 (needed by package2) |
61 |
part5 (needed by both package1 and package2) |
62 |
package1 |
63 |
|
64 |
There should be an error message listing all others. Also, i would add them |
65 |
to world and then emerge so that --update would try to emerge them again, |
66 |
asking me about all previously failed packages when i start it, if i want to |
67 |
retry this time (yes, no, all, none). |
68 |
|
69 |
-- |
70 |
> Kind Regards, |
71 |
> |
72 |
> Simon Stelling |
73 |
> Gentoo/AMD64 Developer |
74 |
> -- |
75 |
> gentoo-portage-dev@g.o mailing list |
76 |
> |
77 |
> |
78 |
|
79 |
|
80 |
-- |
81 |
tvali |
82 |
(e-mail: "qtvali@×××××.com"; msn: "qtvali@×××××.com"; |
83 |
icq: "317-492-912") |
84 |
|
85 |
Ühe eesti internetifirma lehel kohtasin tsitaati: |
86 |
If you don't do it excellently, dont do it at all. Because if it's not |
87 |
excellent, it won't be profitable or fun, and if you're not in business for |
88 |
fun or profit, what the hell are you doing here? |
89 |
Robert Townsend |