1 |
I did think about some priorities too, so that it could be perfect for me. |
2 |
|
3 |
It should be possible to add package with a priority. I will give you an use |
4 |
case and explanation how i would use portage. |
5 |
|
6 |
emerge --justadd kdebase-meta kicker --priority 10 |
7 |
emerge --justadd kdenetwork-meta kdeutils-meta kdeadmin-meta --priority 9 |
8 |
emerge --justadd kdeedu-meta kdetoys-meta kdegames-meta kdeartwork-meta |
9 |
--priority 1 |
10 |
emerge --justadd koffice-meta kdegraphics-meta kdemultimedia-meta --priority |
11 |
5 |
12 |
emerge --justadd kdewebdev-meta kdevelop htmltidy kompare cervisia |
13 |
--priority 7 |
14 |
emerge --justadd kdepim-meta --priority 3 |
15 |
emerge --justadd kdeaddons-meta kde-meta --priority 20 |
16 |
emerge --changepriority kdeaddons-meta kde-meta --priority 0 |
17 |
|
18 |
Now, when i run emerge --update, it should: |
19 |
|
20 |
* Sort packages in such order that packages with highest priority would be |
21 |
installed as soon as possible |
22 |
* Start installing |
23 |
* If something goes wrong, then skip this package and all, which depend on |
24 |
it. This should be optional, if those, which dont depend on it, but are |
25 |
needed by same package, will stay in their positions (go to end of same |
26 |
priority packages) or go to end. |
27 |
|
28 |
When i need to use my computer and need much resources, i will press ctrl-c, |
29 |
use it, then start (continue) emerge --update. |
30 |
|
31 |
2006/3/14, tvali <qtvali@×××××.com>: |
32 |
> |
33 |
> 2006/3/14, Simon Stelling <blubb@g.o>: |
34 |
> > |
35 |
> > tvali wrote: |
36 |
> > > * Add package to "world" checking all dependencies, but not emerging |
37 |
> > > * Remove package from "world" without unmerging |
38 |
> > |
39 |
> > Uhm, why would you want that? |
40 |
> > |
41 |
> |
42 |
> On my computer, building takes several hours on some packages. I have used |
43 |
> it in such way that it builds in several windows on the same time, but i |
44 |
> guess that that's not at all the best practice, especially with some |
45 |
> combinations of packages. So i would like to add all packages, seeing all |
46 |
> blocks and inter dependencies, then start building when ready (and go out of |
47 |
> home, when it builds, and be sure that it will do it's best when i'm away). |
48 |
> |
49 |
> > * Save all important messages into file instead of beeping (i may be |
50 |
> > away |
51 |
> > > from home); optionally replay them at end of update |
52 |
> > |
53 |
> > elog can do this. |
54 |
> |
55 |
> |
56 |
> Will check out. |
57 |
> |
58 |
> > * When updating or installing new package, if something goes wrong, |
59 |
> > still |
60 |
> > > emerge other packages, which havent failed packages as dependencies -- |
61 |
> > in my |
62 |
> > > case, for example, when i do --update, for example, then the fact that |
63 |
> > > update of first package fails does not definitely mean that i dont |
64 |
> > want to |
65 |
> > > update others |
66 |
> > |
67 |
> > --resume |
68 |
> |
69 |
> |
70 |
> I know --resume, but that's not what i meant. |
71 |
> |
72 |
> Imagine the situation: |
73 |
> emerge -p package1 package2 |
74 |
> |
75 |
> part1 (needed by package1) |
76 |
> part2 (needed by part3) |
77 |
> part3 (needed by package2) |
78 |
> part4 (needed by package2) |
79 |
> part5 (needed by both package1 and package2) |
80 |
> package1 |
81 |
> package2 |
82 |
> |
83 |
> now i start "emerge package1 package2" and go to work (or sleep or party |
84 |
> or sauna). |
85 |
> |
86 |
> part2 fails -- some bug or misconfiguration. |
87 |
> |
88 |
> currently it means that when i came back home, i see that part1 is built, |
89 |
> but nothing more and 4-5 hours are actually just wasted. |
90 |
> |
91 |
> There should be a way to have all those built when i came home: |
92 |
> |
93 |
> part1 (needed by package1) |
94 |
> part4 (needed by package2) |
95 |
> part5 (needed by both package1 and package2) |
96 |
> package1 |
97 |
> |
98 |
> There should be an error message listing all others. Also, i would add |
99 |
> them to world and then emerge so that --update would try to emerge them |
100 |
> again, asking me about all previously failed packages when i start it, if i |
101 |
> want to retry this time (yes, no, all, none). |
102 |
> |
103 |
> -- |
104 |
> > Kind Regards, |
105 |
> > |
106 |
> > Simon Stelling |
107 |
> > Gentoo/AMD64 Developer |
108 |
> > -- |
109 |
> > gentoo-portage-dev@g.o mailing list |
110 |
> > |
111 |
> > |
112 |
> |
113 |
> |
114 |
> -- |
115 |
> tvali |
116 |
> (e-mail: "qtvali@×××××.com"; msn: " qtvali@×××××.com"; |
117 |
> icq: "317-492-912") |
118 |
> |
119 |
> Ühe eesti internetifirma lehel kohtasin tsitaati: |
120 |
> If you don't do it excellently, dont do it at all. Because if it's not |
121 |
> excellent, it won't be profitable or fun, and if you're not in business for |
122 |
> fun or profit, what the hell are you doing here? |
123 |
> Robert Townsend |
124 |
> |
125 |
|
126 |
|
127 |
|
128 |
-- |
129 |
tvali |
130 |
(e-mail: "qtvali@×××××.com"; msn: "qtvali@×××××.com"; |
131 |
icq: "317-492-912") |
132 |
|
133 |
Ühe eesti internetifirma lehel kohtasin tsitaati: |
134 |
If you don't do it excellently, dont do it at all. Because if it's not |
135 |
excellent, it won't be profitable or fun, and if you're not in business for |
136 |
fun or profit, what the hell are you doing here? |
137 |
Robert Townsend |