| 1 |
On 17/12/2014 09:45, Helmut Jarausch wrote: |
| 2 |
> On 12/17/2014 06:48:55 AM, meino.cramer@×××.de wrote: |
| 3 |
> .... |
| 4 |
>> Is it possible, to do ONE call to emerge, which asks (according |
| 5 |
>> to option -a, if set ) and given a yes first fetches ALL necessary |
| 6 |
>> files and data and compiles then everything? |
| 7 |
>> |
| 8 |
> |
| 9 |
> With some manual operations: |
| 10 |
> |
| 11 |
> Capture the output of emerge -vp .... |
| 12 |
> Edit it to call |
| 13 |
> ebuild <full patch to <package>.ebuild> fetch |
| 14 |
> for each package. |
| 15 |
> |
| 16 |
> Then issue emerge without -p |
| 17 |
|
| 18 |
|
| 19 |
Way too complicated. |
| 20 |
|
| 21 |
emerge -pvuND world |
| 22 |
|
| 23 |
check list, ensure everything is OK, etc etc. Then |
| 24 |
|
| 25 |
emerge -vunDf world |
| 26 |
emerge -vuND world |
| 27 |
|
| 28 |
-f only fetches, it does not compile. When it completes, switch the pc |
| 29 |
off. The last emerge compiles and everything has been fetched (well |
| 30 |
usually is has been fetched). |
| 31 |
|
| 32 |
|
| 33 |
What the OP is trying to do is not really possible. Portage is designed |
| 34 |
with an assumption in mind: the host is always connected to the internet |
| 35 |
and can fetch whatever it needs to fetch whenever it needs to fetch it |
| 36 |
based on what is in the ebuilds. 100% off-line operation is not part of |
| 37 |
the spec, so the OP is always going to have to deal with occasional |
| 38 |
emerge failures due to the host being offline |
| 39 |
|
| 40 |
-- |
| 41 |
Alan McKinnon |
| 42 |
alan.mckinnon@×××××.com |
Archives