| 1 |
Michael Orlitzky wrote: |
| 2 |
> On 01/02/2012 11:25 AM, Frank Steinmetzger wrote: |
| 3 |
>> |
| 4 |
>> Look at it this way: |
| 5 |
>> with emerge<package> you tell portage to install a package and add |
| 6 |
>> it to |
| 7 |
>> world. Period. The package will be installed, no matter whether it’s |
| 8 |
>> at the |
| 9 |
>> newest version or not. With -u, however, you tell emerge to only do the |
| 10 |
>> installation if the package is actually upgradable. So it’s not an |
| 11 |
>> action |
| 12 |
>> (“upgrade this package”), but an option (“install only if upgradable”). |
| 13 |
> |
| 14 |
> I have no problem seeing it that way, and don't have a semantic |
| 15 |
> preference for one or the other. My problem is that the current |
| 16 |
> behavior can screw up your world file, whereas the old behavior could |
| 17 |
> not. |
| 18 |
> |
| 19 |
> |
| 20 |
|
| 21 |
Plus the only way to fix this is to override it in make.conf with the |
| 22 |
--oneshot option. To me, when you have to fix something like this, |
| 23 |
something is not done right. |
| 24 |
|
| 25 |
I like the way Frank explained this. That was my point way back. |
| 26 |
|
| 27 |
Dale |
| 28 |
|
| 29 |
:-) :-) |
| 30 |
|
| 31 |
-- |
| 32 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
| 33 |
|
| 34 |
Miss the compile output? Hint: |
| 35 |
EMERGE_DEFAULT_OPTS="--quiet-build=n" |
Archives