| 1 |
On 12/02 09:30, Michael Orlitzky wrote: |
| 2 |
> On 12/02/2017 09:15 PM, tuxic@××××××.de wrote: |
| 3 |
> > Hi, |
| 4 |
> > |
| 5 |
> > the instruction of the news item about the swicth to profile 17 says |
| 6 |
> > that one needs to rebuild @world. |
| 7 |
> > |
| 8 |
> > Is this technically needed? |
| 9 |
> |
| 10 |
> Yes, unless you were already using a hardened toolchain. |
| 11 |
> |
| 12 |
> |
| 13 |
> > Would it be possible to do this on base of the daily updates intead |
| 14 |
> > all in one go? |
| 15 |
> |
| 16 |
> No, you'll get build failures trying to link new packages against old |
| 17 |
> libraries. |
| 18 |
> |
| 19 |
> However, you can delay switching to the new profile for a while. |
| 20 |
> |
| 21 |
|
| 22 |
Delaying would not solve the problem as it is... |
| 23 |
|
| 24 |
If the compilation will fail at a certain point (and it will fail, |
| 25 |
since this is a complete new thing) -- would it be possible to resume |
| 26 |
even some tweaks, hacks and patches (even certain recompilations) |
| 27 |
would be needed in between? |
| 28 |
|
| 29 |
Can I stop a running emerge @world and resume later? |
| 30 |
|
| 31 |
How does a restarted emerge @world recognizes packages, which are |
| 32 |
already compiled according to the new standard? |
| 33 |
|
| 34 |
Cheers |
| 35 |
Meino |
Archives