Following the discussion me and Azarah had about make commands, I've started thinking of a way to fix this without being too intrusive and I found a bit of a solution following Az's suggestion to use a wrapper script.
Let's see: we already have an emake script, but using it for "make install" is a no-go because it uses -jX from make.conf and that's not good. A solution can be to improve emake wrapper to check if "install" is in its commandline, in which case it can automatically add a -j1 to be safe. The the ebuilds can just use emake install to do the work, and let the profile define the default MAKE variable (gmake or make, we'll see in the mean time). BDEPEND in this case should not list any kind of make. If somethign needs exactly GNU make, it will list gmake in BDEPEND (sys-libs/make), and will set MAKE="gmake" in the ebuild, so that emake will use it. The same when we'll have something needing bsdmake, we'll add a dev-util/bsdmake ebuild sometime in the future, and then just BDEPEND on || ( sys-apps/freebsd-ubin dev-util/bsdmake ) [or just bsdmake depending if the bsdmake ebuild will be used on g/fbsd, too]. Comments? -- Diego "Flameeyes" Pettenò Gentoo Developer - http://dev.gentoo.org/~flameeyes/ (Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)
pgpPTv3nPmONg.pgp
Description: PGP signature
