Bug 607910

Summary:	sys-apps/portage: Redesign FEATURES=multilib-strict to have some sanity
Product:	Portage Development	Reporter:	Michał Górny <mgorny>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	CONFIRMED ---
Severity:	enhancement	CC:	pacho
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Michał Górny archtester

2017-02-01 12:58:03 UTC

FWICS, right now multilib-strict is a blunt tool. Per configuration in make.defaults:

MULTILIB_STRICT_DIRS="/lib32 /lib /usr/lib32 /usr/lib /usr/kde/*/lib32 /usr/kde/*/lib /usr/qt/*/lib32 /usr/qt/*/lib /usr/X11R6/lib32 /usr/X11R6/lib"
MULTILIB_STRICT_DENY="64-bit.*shared object"
MULTILIB_STRICT_EXEMPT="(perl5|gcc|gcc-lib|binutils|eclipse-3|debug|portage|udev|systemd|clang|python-exec|llvm)"

1. It only bluntly tries to catch 64-bit objects in predefined list of directories,

2. it needs a lot of exemptions to handle 'lib as libexec' case,

3. it needs to be enabled conditionally to profile.


I think it'd be much more reasonable to have multilib-strict that:

1. Respects LIBDIR_* and checks each for ABI-specific libraries/executables,

2. is aware of 'lib as libexec', and therefore doesn't need lot of pointless exemptions.