1 |
Thanks for your prompt response. |
2 |
|
3 |
It would be very useful I think to have a small tool to continue a merge |
4 |
from a certain point, for example by selecting the package name you want |
5 |
to continue from. |
6 |
|
7 |
Example: eresume dev-db/mysql |
8 |
|
9 |
Would just look in the /var/cache/edb/mtimedb file for 'dev-db/mysql' and |
10 |
continue. |
11 |
|
12 |
It could be an emerge feature: |
13 |
|
14 |
Example: emerge --resume --from dev-db/mysql |
15 |
|
16 |
I might look in to coding something. |
17 |
|
18 |
Thanks. |
19 |
|
20 |
On Thu, 06 Apr 2006 14:55:53 +1000, Alec Warner <antarus@g.o> wrote: |
21 |
|
22 |
> evader wrote: |
23 |
>> Hi, |
24 |
>> |
25 |
>> I'm not sure if this is the correct list to send this too, but it is |
26 |
>> the only gentoo one I am currently subscribed to. |
27 |
>> |
28 |
>> When I do an emerge -e world where is the list of files to be merged |
29 |
>> stored? For example if I break an emerge, and want to resume later from |
30 |
>> a different position, can I edit the packages to be emerged list so I |
31 |
>> don't have to do emerge --resume --skipfirst constantly? |
32 |
>> |
33 |
>> Thanks, |
34 |
>> |
35 |
>> evader |
36 |
> |
37 |
> The list is stored in a small database file in /var/cache/edb/mtimedb |
38 |
> |
39 |
> It is a binary file full of pickled python objects. I was actually |
40 |
> poking around it and thought about writing a tool. I will commit more |
41 |
> time to it if you are interested; although be warned that editing things |
42 |
> in that file is not particularly recommended. The dependency resolution |
43 |
> for the packages in the list is done and the list is created. Removing |
44 |
> items from it could cause packages to not build, and the dependency tree |
45 |
> to essentially be broken for that list. |
46 |
> |
47 |
> Also, portage questions are generally well received at |
48 |
> gentoo-portage-dev@g.o, or on IRC: irc.freenode.net |
49 |
> #gentoo-portage. |
50 |
> |
51 |
> -Alec Warner |
52 |
|
53 |
|
54 |
-- |
55 |
gentoo-dev@g.o mailing list |