alsa-tools can employ a similar approach as alsa-driver to let the user specify what tools they want to install. It would be a nice feature, since most of the tools are hardware specific. I don't know about the DEPEND, but it should be safe to leave it at as it is. --- /usr/portage/media-sound/alsa-tools/alsa-tools-1.0.0_rc2-r1.ebuild 2004-01-03 23:55:11.000000000 +0900 +++ alsa-tools-1.0.1.ebuild 2004-01-10 21:29:43.348891102 +0900 @@ -17,7 +17,7 @@ LICENSE="GPL-2" S=${WORKDIR}/${MY_P} -DEPEND=">=media-libs/alsa-lib-1.0.0_rc2 +DEPEND=">=media-libs/alsa-lib-${PV} virtual/alsa =x11-libs/fltk-1.1* =x11-libs/gtk+-1.2*" @@ -25,6 +25,7 @@ # This is a list of the tools in the package. # Some of the tools don't make proper use of CFLAGS, even though # all of them seem to use autoconf. This needs to be fixed. +[ x"${ALSA_TOOLS}" = x ] && \ ALSA_TOOLS="ac3dec as10k1 envy24control hdspconf hdsploader hdspmixer \ mixartloader rmedigicontrol sb16_csp seq/sbiload sscape_ctl \ us428control usx2yloader vxloader"
now in portage...
There is a small typo in the ebuild. It says: # environment to a space-separated list of toolss that you want to build.
ppicky, pickky ;) I comited thhe fixx.