1 |
The 2016-06-20 17:52, Ian Bloss wrote : |
2 |
|
3 |
> Usually what I'll do is ctrl-z which pauses emerge, and then I'll run |
4 |
> pm-suspend to put the machine to sleep. After I turn it back on again |
5 |
> I'll issue fg and emerge will resume. |
6 |
|
7 |
The 2016-06-20 18:29, Mick wrote : |
8 |
|
9 |
> In addition, if you can use the same procedure for hibernate (to disk) |
10 |
> if for |
11 |
> some reason you need to completely remove power from your PC. |
12 |
|
13 |
Yes, I know that but I was in a special case where I couldn't use it. |
14 |
|
15 |
|
16 |
|
17 |
|
18 |
The 2016-06-20 17:56, Andrew Lowe wrote : |
19 |
|
20 |
> What I do may be of help, but then again, it may be all wrong and one |
21 |
> day the gates of hell may open up and swallow mankind because of what I |
22 |
> did, but hey, that's life. |
23 |
> |
24 |
> There is the FEATURES entry in make.conf, man make.conf. Within this |
25 |
> are two options "keeptemp" and "keepwork". I enable them, then the |
26 |
> consequences of which is that stuff is not cleaned up. Hence when I |
27 |
> rerun the emerge, the "make" within sees the already existing files and |
28 |
> skips them, in other words it does as "make" is expected to do. |
29 |
> |
30 |
> Please bear in mind if you have /var/tmp/portage set up to be a RAM |
31 |
> disk of some sort, obviously if you turn your machine off, you'll look |
32 |
> the intermediate files, but if you are hard disk based, they will be |
33 |
> there when you restart the machine and so when you rerun emerge, the |
34 |
> part up until when you killed the emerge originally will be skipped. |
35 |
> |
36 |
> Hope this helps, |
37 |
> Andrew |
38 |
|
39 |
Hey, this is an instrosting option ! Thank you ! |
40 |
|
41 |
|
42 |
|
43 |
The 2016-06-20 18:12, Marc Stürmer wrote : |
44 |
|
45 |
> Take a look at Tux on Ice, this should do the trick for you. |
46 |
|
47 |
I already have suspend and hibernate command. Is it different ? |
48 |
|
49 |
|
50 |
|
51 |
The 2016-06-20 18:41, Raffaele BELARDI wrote : |
52 |
|
53 |
> I had success in the past using ebuild instead of emerge. Check the man |
54 |
> page, briefly emerge is equivalent to the following steps in sequence: |
55 |
> |
56 |
> $ ebuild fetch |
57 |
> $ ebuild unpack |
58 |
> $ ebuild compile |
59 |
> $ ebuild install |
60 |
> $ ebuild qmerge |
61 |
> |
62 |
> Running 'make' in the temp dir followed by the last two ebuild steps |
63 |
> only (install and qmerge) should work. |
64 |
> |
65 |
> raffaele |
66 |
|
67 |
Thank you very much for this little course ! It's very introsting ! |
68 |
And it help me very much ! |
69 |
|
70 |
|
71 |
|
72 |
The 2016-06-20 18:42, Willie M wrote : |
73 |
|
74 |
> This is pretty much what is run when you emerge something. |
75 |
> |
76 |
> ebuild [.ebuild] fetch |
77 |
> ebuild [.ebuild] unpack |
78 |
> ebuild [.ebuild] compile |
79 |
> ebuild [.ebuild] install |
80 |
> ebuild [.ebuild] qmerge |
81 |
> ebuild [.ebuild] clean |
82 |
> |
83 |
> to continue just choose what part the build was on when you quit it and |
84 |
> start there. |
85 |
> |
86 |
> All I really just use is compile and merge. If it didn't get to compile |
87 |
> it isn't worth it. Just emerge the whole thing again. |
88 |
|
89 |
Thank you for your additional informations ! |
90 |
|
91 |
|
92 |
The 2016-06-20 22:52, "J." García wrote : |
93 |
|
94 |
> Yes you can, it is not officially supported to do this but I have done |
95 |
> it several times (webkits, libreoffice) without problems, what I do is |
96 |
> make a binary package and then install it, you should have set $PKGDIR |
97 |
> in make.conf, here's how I've done it: |
98 |
> |
99 |
> You stopped at libreoffice, you restart your computer, then you should |
100 |
> find out what is the exact ebuild you were building, equery can help |
101 |
> you, if it is an upgrade, i.e.: |
102 |
> |
103 |
> $ equery which libreoffice |
104 |
> ${PORDIR}/app-office/libreoffice/libreoffice-5.1.3.2.ebuild |
105 |
> |
106 |
> then you pretend you are emerge, by using the portage user to make the |
107 |
> build resume, make sure $PKGDIR is writable by the portage user: |
108 |
> |
109 |
> $ sudo -u portage ebuild\ |
110 |
> ${PORTDIR}/app-office/libreoffice/libreoffice-5.1.3.2.ebuild \ |
111 |
> package |
112 |
> |
113 |
> or nesting both commands: |
114 |
> |
115 |
> $ sudo -u portage ebuild $(equery w libreoffice) package |
116 |
> |
117 |
> this makes all the previous steps needed (prepare, configure ,build, |
118 |
> install) if they haven't been done, |
119 |
> when that is finished you can merge your recently created binary |
120 |
> package by: |
121 |
> |
122 |
> $ sudo emerge -av1K =app-office/libreoffice-5.1.3.2 |
123 |
> |
124 |
> and resume the general upgrade with: |
125 |
> |
126 |
> emerge --resume -av --exclude app-office/libreoffice |
127 |
|
128 |
Thank you for your alternate method ! |
129 |
|
130 |
|
131 |
|
132 |
|
133 |
Thank you all, very very much for this lot of introsting and helpful |
134 |
anwsers ! |
135 |
|
136 |
|
137 |
Hogren |