| 1 |
On Mon, Jun 28, 2010 at 10:12 AM, Mark Knecht <markknecht@×××××.com> wrote: |
| 2 |
> On Mon, Jun 28, 2010 at 9:55 AM, <meino.cramer@×××.de> wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> is it possible to emerge all missing dependencies of a certain |
| 6 |
>> application without emerging the application itself? And: Will |
| 7 |
>> I hurt the system that way? |
| 8 |
>> |
| 9 |
>> Best regards, |
| 10 |
>> mcc |
| 11 |
> |
| 12 |
> ??? |
| 13 |
> |
| 14 |
> emerge -DuN application |
| 15 |
> |
| 16 |
> ??? |
| 17 |
> |
| 18 |
> What am I missing in the question? |
| 19 |
> |
| 20 |
> Test it on a clean app with no dependencies missing. It should emerge |
| 21 |
> nothing. Then emerge -C one dependency and try it again. It should |
| 22 |
> pick up that dependency but not emerge the app itself. |
| 23 |
> |
| 24 |
> You will not hurt your system doing that command. |
| 25 |
> |
| 26 |
> - Mark |
| 27 |
> |
| 28 |
|
| 29 |
I wanted to follow up on my somewhat cavalier comment a couple of days |
| 30 |
ago about doing emerge -C on a dependency. It was a bad comment for me |
| 31 |
to make without adding some discussion around it. This can actually |
| 32 |
harm your system if you emerge -C the wrong dependency. For instance, |
| 33 |
emerge -C gcc or python is likely a bad thing to do as you will be |
| 34 |
unable to build anything to get the system fixed again. However emerge |
| 35 |
-C jack-audio-connection-kit as a dependency for something like Ardour |
| 36 |
wouldn't harm the system but would demonstrate what I was talking |
| 37 |
about. |
| 38 |
|
| 39 |
Any new user reading this thread at some future date should ensure |
| 40 |
that (at a minimum) if they emerge -C anything at all that at least |
| 41 |
it's not part of @system. emerge should warn of this but it's best to |
| 42 |
do a little study before pushing the enter key. |
| 43 |
|
| 44 |
Cheers, |
| 45 |
Mark |
Archives