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