Gentoo Archives: gentoo-portage-dev

From: tvali <qtvali@×××××.com>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Few things, which imho would make portage better
Date: Tue, 14 Mar 2006 13:27:01
Message-Id: cea53e3c0603140525p64760f9cg@mail.gmail.com
In Reply to: Re: [gentoo-portage-dev] Few things, which imho would make portage better by Devon Miller
1 Thank you much!
2
3 This is what i meant about searching :) Would it be now good to mix
4 this esearch code with emerge, then adding fields to db and making
5 emerge treebuilding fast, too? Or is there some utility to emerge,
6 which does all that?
7
8 2006/3/14, Devon Miller <devon.c.miller@×××××.com>:
9 > Try "emerge esearch". Replace "emerge --sync" with "esync", "emerge -s" with
10 > "esearch", and "emerge -S" with "esearch -S".
11 > After running "emerge --update ...", run "eupdatedb".
12 >
13 > As for dependency tree: "emerge --pretend --tree world"
14 > Or, to also check additional dependencies: "emerge --deep --pretend --tree
15 > world"
16 > And, if you want to see how *everything* relates: "emerge --deep --emptytree
17 > --pretend --tree"
18 >
19 > dcm
20 >
21 >
22 >
23 > On 3/14/06, tvali <qtvali@×××××.com> wrote:
24 > >
25 > > Another place, where it would be good, is that it could interact well with
26 > GUI and it's Apply button.
27 > >
28 > > Another thing, what would be imho improved, is the speed of following
29 > functions:
30 > > * emerge -s, emerge -S
31 > > They should be cached somehow.
32 > >
33 > > Also, i think that when speaking about *speed* of portage, which is imho
34 > notably slow right now (speed of searching, building trees and so on),
35 > sql-support should be considered. In /usr/portage/, i see many folders and
36 > files, which tend to contain one or two words, lists of hashes and so on.
37 > Actually i see relational database there. With many caches and other
38 > optimizations it could be tuned fast, but having SQL doing all that, it
39 > would be achieved very simply (maybe it would be a jump to have all linux
40 > configurations in one SQL "filesystem"? ...ok, just fantasy:))
41 > >
42 > > There are several small and simple SQL databases. With such tool, big
43 > parts of portage become unnessecary, but it's speed will become much faster.
44 > This should be optional if one uses some tiny sql, mysql or big clustered
45 > sql with nas and load-balancer, but by default some tiny version of SQL
46 > should be built.
47 > >
48 > > Also, i currently dont see a possibility to see dependency tree of
49 > installed package.
50 > >
51 > >
52 > >
53 > > 2006/3/14, tvali < qtvali@×××××.com>:
54 > > > I did think about some priorities too, so that it could be perfect for
55 > me.
56 > > >
57 > > > It should be possible to add package with a priority. I will give you an
58 > use case and explanation how i would use portage.
59 > > >
60 > > > emerge --justadd kdebase-meta kicker --priority 10
61 > > > emerge --justadd kdenetwork-meta kdeutils-meta kdeadmin-meta --priority
62 > 9
63 > > > emerge --justadd kdeedu-meta kdetoys-meta kdegames-meta kdeartwork-meta
64 > --priority 1
65 > > > emerge --justadd koffice-meta kdegraphics-meta kdemultimedia-meta
66 > --priority 5
67 > > > emerge --justadd kdewebdev-meta kdevelop htmltidy kompare cervisia
68 > --priority 7
69 > > > emerge --justadd kdepim-meta --priority 3
70 > > > emerge --justadd kdeaddons-meta kde-meta --priority 20
71 > > > emerge --changepriority kdeaddons-meta kde-meta --priority 0
72 > > >
73 > > > Now, when i run emerge --update, it should:
74 > > >
75 > > > * Sort packages in such order that packages with highest priority would
76 > be installed as soon as possible
77 > > > * Start installing
78 > > > * If something goes wrong, then skip this package and all, which depend
79 > on it. This should be optional, if those, which dont depend on it, but are
80 > needed by same package, will stay in their positions (go to end of same
81 > priority packages) or go to end.
82 > > >
83 > > > When i need to use my computer and need much resources, i will press
84 > ctrl-c, use it, then start (continue) emerge --update.
85 > > >
86 > > >
87 > > > 2006/3/14, tvali <qtvali@×××××.com>:
88 > > >
89 > > > > 2006/3/14, Simon Stelling <blubb@g.o>:
90 > > > >
91 > > > > > tvali wrote:
92 > > > > > > * Add package to "world" checking all dependencies, but not
93 > emerging
94 > > > > > > * Remove package from "world" without unmerging
95 > > > > >
96 > > > > > Uhm, why would you want that?
97 > > > > >
98 > > > >
99 > > > >
100 > > > > On my computer, building takes several hours on some packages. I have
101 > used it in such way that it builds in several windows on the same time, but
102 > i guess that that's not at all the best practice, especially with some
103 > combinations of packages. So i would like to add all packages, seeing all
104 > blocks and inter dependencies, then start building when ready (and go out of
105 > home, when it builds, and be sure that it will do it's best when i'm away).
106 > > > >
107 > > > >
108 > > > > > > * Save all important messages into file instead of beeping (i may
109 > be away
110 > > > > > > from home); optionally replay them at end of update
111 > > > > >
112 > > > > > elog can do this.
113 > > > >
114 > > > >
115 > > > > Will check out.
116 > > > >
117 > > > >
118 > > > > > > * When updating or installing new package, if something goes
119 > wrong, still
120 > > > > > > emerge other packages, which havent failed packages as
121 > dependencies -- in my
122 > > > > > > case, for example, when i do --update, for example, then the fact
123 > that
124 > > > > > > update of first package fails does not definitely mean that i dont
125 > want to
126 > > > > > > update others
127 > > > > >
128 > > > > > --resume
129 > > > >
130 > > > >
131 > > > > I know --resume, but that's not what i meant.
132 > > > >
133 > > > > Imagine the situation:
134 > > > > emerge -p package1 package2
135 > > > >
136 > > > > part1 (needed by package1)
137 > > > > part2 (needed by part3)
138 > > > > part3 (needed by package2)
139 > > > > part4 (needed by package2)
140 > > > > part5 (needed by both package1 and package2)
141 > > > > package1
142 > > > > package2
143 > > > >
144 > > > > now i start "emerge package1 package2" and go to work (or sleep or
145 > party or sauna).
146 > > > >
147 > > > > part2 fails -- some bug or misconfiguration.
148 > > > >
149 > > > > currently it means that when i came back home, i see that part1 is
150 > built, but nothing more and 4-5 hours are actually just wasted.
151 > > > >
152 > > > > There should be a way to have all those built when i came home:
153 > > > >
154 > > > > part1 (needed by package1)
155 > > > > part4 (needed by package2)
156 > > > > part5 (needed by both package1 and package2)
157 > > > > package1
158 > > > >
159 > > > > There should be an error message listing all others. Also, i would add
160 > them to world and then emerge so that --update would try to emerge them
161 > again, asking me about all previously failed packages when i start it, if i
162 > want to retry this time (yes, no, all, none).
163 > > > >
164 > > > >
165 > > > > > --
166 > > > > > Kind Regards,
167 > > > > >
168 > > > > > Simon Stelling
169 > > > > > Gentoo/AMD64 Developer
170 > > > > > --
171 > > > > > gentoo-portage-dev@g.o mailing list
172 > > > > >
173 > > > > >
174 > > > >
175 > > > >
176 > > > >
177 > > > >
178 > > > > --
179 > > > > tvali
180 > > > > (e-mail: " qtvali@×××××.com"; msn: " qtvali@×××××.com";
181 > > > > icq: "317-492-912")
182 > > > >
183 > > > > Ühe eesti internetifirma lehel kohtasin tsitaati:
184 > > > > If you don't do it excellently, dont do it at all. Because if it's not
185 > excellent, it won't be profitable or fun, and if you're not in business for
186 > fun or profit, what the hell are you doing here?
187 > > > > Robert Townsend
188 > > >
189 > > >
190 > > >
191 > > >
192 > > > --
193 > > > tvali
194 > > > (e-mail: " qtvali@×××××.com"; msn: "qtvali@×××××.com";
195 > > > icq: "317-492-912")
196 > > >
197 > > > Ühe eesti internetifirma lehel kohtasin tsitaati:
198 > > > If you don't do it excellently, dont do it at all. Because if it's not
199 > excellent, it won't be profitable or fun, and if you're not in business for
200 > fun or profit, what the hell are you doing here?
201 > > > Robert Townsend
202 > >
203 > >
204 > >
205 > > --
206 > > tvali
207 > > (e-mail: "qtvali@×××××.com"; msn: " qtvali@×××××.com";
208 > > icq: "317-492-912")
209 > >
210 > > Ühe eesti internetifirma lehel kohtasin tsitaati:
211 > > If you don't do it excellently, dont do it at all. Because if it's not
212 > excellent, it won't be profitable or fun, and if you're not in business for
213 > fun or profit, what the hell are you doing here?
214 > > Robert Townsend
215 >
216 >
217
218
219 --
220 tvali
221 (e-mail: "qtvali@×××××.com"; msn: "qtvali@×××××.com";
222 icq: "317-492-912")
223
224 Ühe eesti internetifirma lehel kohtasin tsitaati:
225 If you don't do it excellently, dont do it at all. Because if it's not
226 excellent, it won't be profitable or fun, and if you're not in
227 business for fun or profit, what the hell are you doing here?
228 Robert Townsend
229
230 --
231 gentoo-portage-dev@g.o mailing list

Replies