Bug 224341

Summary:	MAKEOPTS-checking code from paludis should be in some eclass
Product:	Gentoo Linux	Reporter:	David Watzke <david>
Component:	New packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED REMIND
Severity:	normal	CC:	fischer
Priority:	High
Version:	2008.0
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description David Watzke 2008-05-31 15:50:17 UTC

Hi, I'd like to suggest moving the MAKEOPTS-checking code from paludis ebuild (in the pkg_setup() function) to some eclass, so it can be easily used elsewhere. Number of MB of the free memory per thread should be optional, I guess.

Comment 1 Jeroen Roovers (RETIRED) gentoo-dev

2008-06-01 19:20:32 UTC

Reopen this bug when this is more than just a good idea.

Comment 2 David Watzke 2008-06-01 19:28:34 UTC

That means "when there's any particular use for it" or "when you come up with the eclass"?

Comment 3 Thomas Fischer 2008-08-05 17:07:07 UTC

I wonder if checking MAKEOPTS (in particular -jX) is a good idea for three reasons:
- The currently implementation does not consider distcc configurations, slowing down the compilation process
- Following the Gentoo philosophy, the system should not force the user to some settings unless neccessary (printing warnings is ok)
- There is Gentoo-specific documentation available on setting -jX to a system-specific value, so any user with some understanding will set this switch to his/her preferred value anyways.