emerging museek+-0.1.13-r1 fails if cmake is not installed. Adding cmake to museek+ DEPEND fixes problem. Reproducible: Didn't try Steps to Reproduce: 1. emerge -C cmake museek+ 2. emerge =museek+-0.1.13-r1 Actual Results: >>> Unpacking source... >>> Unpacking museek+-0.1.13.tar.bz2 to /var/tmp/portage/net-p2p/museek+-0.1.13-r1/work * Applying museek+-0.1.13-optional-deps.patch ... [ ok ] * Applying museek+-0.1.13-post_release_fixes.patch ... [ ok ] >>> Source unpacked. >>> Compiling source in /var/tmp/portage/net-p2p/museek+-0.1.13-r1/work/museek+-0.1.13 ... /usr/portage/net-p2p/museek+/museek+-0.1.13-r1.ebuild: line 66: cmake: command not found I have a problem emerging museek+: It seems that the new museek+ has switched to using cmake as the default build tool, as stated in the changelog: Museek+ Change Log 0.1.13 Released August 25th 2007 BUILD SYSTEMS CMake, qmake, SCons and Python's distutils * RECOMMENDED: cmake * CMake compiles and installs everything. Read the INSTALL files for details. * qmake compiles just museeq. Read museeq/INSTALL * You can install the python bindings, apps, and clients with distutils. Run "python setup.py install" in each python sub-directory * SCons is still available, but not recommended. Read INSTALL.scons Adding dev-util/cmake to DEPEND in the ebuild worked for me: DEPEND="${RDEPEND} dev-util/cmake dev-lang/swig"
(In reply to comment #0) > Reproducible: Didn't try is a mistake ... I have reproduced it.
I fixed it a coupe of hours ago. Sync the tree and try again ;-)
