This is the tracker bug for the vmware-player ebuilds from the vmware overlay. This is split off to try to reduce the pressure on bug #122500 by separating out issues to specific packages.
I appreciate the move to separate vmware.eclass, but the recent ebuild bombs out in 'doman': # emerge -avu1 vmware-player ... [ebuild U ] app-emulation/vmware-player-1.0.1.19317-r4 [1.0.1.19317-r3] 0 kB ... >>> Install vmware-player-1.0.1.19317-r4 into /var/tmp/portage/vmware-player-1.0.1.19317-r4/image/ category app-emulation doman: 'FILES/*' is probably not a man page; skipping !!! ERROR: app-emulation/vmware-player-1.0.1.19317-r4 failed. Call stack: ebuild.sh, line 1543: Called dyn_install ebuild.sh, line 1017: Called src_install vmware-player-1.0.1.19317-r4.ebuild, line 56: Called vmware_src_install vmware.eclass, line 185: Called die I'm using portage-2.1.1_pre4-r4 and baselayout-1.12.4-r2 ATM.
Confirmed on amd64. Same bomb. Same place. W
Same problem here. $ emerge --info Portage 2.1.1_pre4-r4 (default-linux/x86/2006.0, gcc-4.1.1/vanilla, glibc-2.4-r3, 2.6.17-gentoo-r5 i686) ================================================================= System uname: 2.6.17-gentoo-r5 i686 Intel(R) Xeon(TM) CPU 3.20GHz Gentoo Base System version 1.12.4 Last Sync: Thu, 10 Aug 2006 15:30:01 +0000 ccache version 2.4 [disabled] app-admin/eselect-compiler: 2.0.0_rc2-r1 dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r2 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.60 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.17 sys-devel/gcc-config: 2.0.0_rc1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" ...
Created attachment 93932 [details] vmware.eclass changed to only invoke "doman" when a man directory is present Looks to me like vmware.eclass only cd's into the "man" directory when its present, but nevertheless always tries "doman". The attached vmware.ebuild changes the behaviour to only do doman when the "man" directory actually exists. This allows vmware-player-1.0.1.19317-r4 to successfully install.
(In reply to comment #4) > Created an attachment (id=93932) [edit] > vmware.eclass changed to only invoke "doman" when a man directory is present This patch worked for me.
Ugh... you attached the whole eclass and not a patch... I've committed the updates to CVS and also to SVN. Anyway, I'm marking this bug as FIXED since I've moved the ebuild into the tree and I want people to file individual bugs now.
