1 |
Hi, |
2 |
|
3 |
Further to my email before, a quick hack in the emerge script somewhere |
4 |
here should fix it: |
5 |
# We're resuming. |
6 |
print green("*** Resuming merge...") |
7 |
emergelog(" *** Resuming merge...") |
8 |
mymergelist=portage.mtimedb["resume"]["mergelist"][:] |
9 |
if ("--skipfirst" in myopts) and mymergelist: |
10 |
del |
11 |
portage.mtimedb["resume"]["mergelist"][0] |
12 |
del mymergelist[0] |
13 |
for bigkey in mymergelist: |
14 |
(pkgtype, root, cpv, action) = bigkey |
15 |
if pkgtype == "binary" and not |
16 |
portage.db["/"]["bintree"].dbapi.match("="+cpv) or \ |
17 |
pkgtype == "ebuild" and not |
18 |
portage.db["/"]["porttree"].dbapi.xmatch("match-all", "="+cpv): |
19 |
|
20 |
This is the first time I've looked at so I'll see how I go. Any tips? |
21 |
|
22 |
evader |
23 |
|
24 |
|
25 |
|
26 |
On Thu, 06 Apr 2006 14:55:53 +1000, Alec Warner <antarus@g.o> wrote: |
27 |
|
28 |
> evader wrote: |
29 |
>> Hi, |
30 |
>> |
31 |
>> I'm not sure if this is the correct list to send this too, but it is |
32 |
>> the only gentoo one I am currently subscribed to. |
33 |
>> |
34 |
>> When I do an emerge -e world where is the list of files to be merged |
35 |
>> stored? For example if I break an emerge, and want to resume later from |
36 |
>> a different position, can I edit the packages to be emerged list so I |
37 |
>> don't have to do emerge --resume --skipfirst constantly? |
38 |
>> |
39 |
>> Thanks, |
40 |
>> |
41 |
>> evader |
42 |
> |
43 |
> The list is stored in a small database file in /var/cache/edb/mtimedb |
44 |
> |
45 |
> It is a binary file full of pickled python objects. I was actually |
46 |
> poking around it and thought about writing a tool. I will commit more |
47 |
> time to it if you are interested; although be warned that editing things |
48 |
> in that file is not particularly recommended. The dependency resolution |
49 |
> for the packages in the list is done and the list is created. Removing |
50 |
> items from it could cause packages to not build, and the dependency tree |
51 |
> to essentially be broken for that list. |
52 |
> |
53 |
> Also, portage questions are generally well received at |
54 |
> gentoo-portage-dev@g.o, or on IRC: irc.freenode.net |
55 |
> #gentoo-portage. |
56 |
> |
57 |
> -Alec Warner |
58 |
|
59 |
|
60 |
-- |
61 |
gentoo-dev@g.o mailing list |