1 |
On Wed, 2009-02-04 at 18:15 -0600, Paul Hartman wrote: |
2 |
> On Wed, Feb 4, 2009 at 5:42 PM, Iain Buchanan <iaindb@××××××××××××.au> wrote: |
3 |
> > |
4 |
> > The emerge log mentioned `emerge |
5 |
> > --config vmware-workstation` which output this: |
6 |
|
7 |
[snip] |
8 |
|
9 |
> > But vmware still complains about vmware-config.pl |
10 |
> > |
11 |
> > Any ideas? |
12 |
> |
13 |
> I think emerge --config is the "gentoo way". |
14 |
> |
15 |
> It runs /opt/vmware/workstation/bin/vmware-networks |
16 |
> |
17 |
> Here's the snippet from the ebuild: |
18 |
> |
19 |
> pkg_config() { |
20 |
> ${VM_INSTALL_DIR}/bin/vmware-networks --postinstall ${PN},old,new |
21 |
> } |
22 |
> |
23 |
|
24 |
It doesn't seem to do what vmware-config used to do, and if it was a |
25 |
replacement for vmware-config, why would VMWware still reference |
26 |
vmware-config.pl? |
27 |
|
28 |
Any ideas on using vmware-networks to reconfigure my, er, vmware |
29 |
networks? It doesn't seem prompt-driven like vmware-config used to be |
30 |
either... (Yes I've looked at the --help option). |
31 |
|
32 |
thanks, |
33 |
-- |
34 |
Iain Buchanan <iaindb at netspace dot net dot au> |
35 |
|
36 |
Patch griefs with proverbs. |
37 |
-- William Shakespeare, "Much Ado About Nothing" |