| 1 |
Hi to all! |
| 2 |
|
| 3 |
Can you please tell me how you solved the problem..Each time i got a: |
| 4 |
[blocks B ] dev-java/java-config-wrapper (is blocking |
| 5 |
dev-java/java-config-1.2.11-r1) |
| 6 |
|
| 7 |
while creating the stage1.. |
| 8 |
I have set all the package like the java upgrade guide in package.keywords... |
| 9 |
|
| 10 |
Thank you |
| 11 |
Luca |
| 12 |
|
| 13 |
Alle 00:19, mercoledì 02 agosto 2006, Ted Kosan ha scritto: |
| 14 |
> Joshua wrote: |
| 15 |
> > Actually, during a fresh install, installing a JDK will set the itself |
| 16 |
> > as the system-vm for you, so you shouldn't have to set it yourself. |
| 17 |
> |
| 18 |
> After experimenting with the various suggestions that Andrew and Chris |
| 19 |
> submitted ( and learning more about how Catalyst works in the process ) I |
| 20 |
> finally figured out that the JDK package was designed to install itself as |
| 21 |
> the system-vm in the first place. |
| 22 |
> |
| 23 |
> I eventually discovered that I did not have the package.keywords file in my |
| 24 |
> portage-overlay configured correctly with the packages given on the |
| 25 |
> java-upgrade page. |
| 26 |
|
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
"Chiunque può simpatizzare col dolore di un amico, ma solo chi ha un animo |
| 31 |
nobile riesce a simpatizzare col successo di un amico (Oscar Wilde)" |
| 32 |
|
| 33 |
LINUX User #411601 |
| 34 |
jabber: casagrande@××××××××××××.it |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-catalyst@g.o mailing list |
Archives