| 1 |
wouldn't it be: |
| 2 |
|
| 3 |
emerge -o package |
| 4 |
|
| 5 |
? |
| 6 |
|
| 7 |
"emerge -DuN package" _will_ install the package itself. |
| 8 |
|
| 9 |
On Mon, Jun 28, 2010 at 2:12 PM, Mark Knecht <markknecht@×××××.com> wrote: |
| 10 |
|
| 11 |
> On Mon, Jun 28, 2010 at 9:55 AM, <meino.cramer@×××.de> wrote: |
| 12 |
> > Hi, |
| 13 |
> > |
| 14 |
> > is it possible to emerge all missing dependencies of a certain |
| 15 |
> > application without emerging the application itself? And: Will |
| 16 |
> > I hurt the system that way? |
| 17 |
> > |
| 18 |
> > Best regards, |
| 19 |
> > mcc |
| 20 |
> |
| 21 |
> ??? |
| 22 |
> |
| 23 |
> emerge -DuN application |
| 24 |
> |
| 25 |
> ??? |
| 26 |
> |
| 27 |
> What am I missing in the question? |
| 28 |
> |
| 29 |
> Test it on a clean app with no dependencies missing. It should emerge |
| 30 |
> nothing. Then emerge -C one dependency and try it again. It should |
| 31 |
> pick up that dependency but not emerge the app itself. |
| 32 |
> |
| 33 |
> You will not hurt your system doing that command. |
| 34 |
> |
| 35 |
> - Mark |
| 36 |
> |
| 37 |
> |
Archives