[Vmware-package-maintainers] Bug#433880: missing debconf prompts

Daniel Knabl daniel at tirolinux.net
Fri Aug 31 14:02:05 UTC 2007


Am Thu, 30 Aug 2007 23:51:52 -0400 schrieb Robert Edmonds
<edmonds at debian.org>:

> > Another problem is, that the vmware-server Debian package seems not
> > to provide multiple bridged interfaces, no multiple NAT-interfaces,
> > and something very annoying, it does NOT provide a way to set the
> > data-dir to something other than /srv/vmware. This should be
> > possible with the debconf interface in an easy way.  Also, the
> > mui-package can have a different port than 902 when running
> > vmware-config-mui.pl, which is not available in the Debian package.
> > Why are those vmware-config*.pl files no longer available? Is there
> > an important issue to remove them from the sources? What about
> > providing the same functionality through debconf? This would really
> > be very important, if you want your package to be useable in
> > production environment.
> 
> the vmware-*.pl install/configure scripts have been removed because
> they interact poorly with the .deb packaging, and because they're
> shipped as huge, monolithic scripts (that do stupid things like
> storing both configuration and primitive package management data in
> /etc/vmware/locations) that would be extremely difficult to extract
> needed or excise unwanted functionality from.  even if these scripts
> could be successfully modified, the modified versions could not be
> distributed in vmware-package.

If you need help with the debconf-scripting or any help in debugging
things I'll be ready to help wherever possible.

Just as a hint for others with the same problems:
There's still the possibility to modify the file /etc/vmware/config so
that it supports more networks/interfaces. One can also build the
modules from the sources and/or from the any-any-patch and copy them
into his system, as long as the versions really are the same. I've
tried this here on some boxes with different kernels, and the modules
were built "manually" from the source tarballs in a "build-machine" on
my VMWare Workstation. Everything seems to work very well.

Many thanks to Robert for his great work.

regards
Daniel

-- 
Daniel Knabl
www.tirolinux.net             daniel at tirolinux.net
PGP/GPG Fingerprint - please send signed mail only
A069 671B 39F2 E9B9 FB34  68BB 4BEC 1344 C8A4 3F0B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/vmware-package-maintainers/attachments/20070831/e2065a85/attachment.pgp 


More information about the Vmware-package-maintainers mailing list