Bug 443590 – sys-apps/portage: Request for automatic QA check for cross / vs. /usr linking (NEEDED entries)

• Product: Gentoo Linux
• Status: RESOLVED WONTFIX

[Description Samuli Suominen (RETIRED) 2012-11-17 10:12:13 UTC]

Now that we udev-ng (fork) is going to be created and some packages will be moved to / from /usr to support it, such as kmod, we need an QA check that checks files in /lib, /lib32, /lib64 for NEEDED entries and prints a warning
at the end of emerge if libraries from / link to libraries in /usr

Otherwise the / will not be maintainable, and it is the main reason that led to this mess we are currently in

As in, the output of `scanelf -n` or possible `objdump` needs to be parsed

This is my main concern with the issues around the udev-ng fork

Thank you!

[Comment 1 Zac Medico 2012-11-29 08:02:09 UTC]

We also need to check binaries in /sbin and /bin, right?

Also should't we check /lib* (not just /lib{,32,64}), since we want to get libx32 as in bug #435834?

[Comment 2 Zac Medico 2012-11-30 02:38:30 UTC]

If anybody wants to try a patch for this, I'd suggest to do something like our existing "Missing soname symlink(s)" check, which parses the NEEDED.ELF.2 file that's created with scanelf:

http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=31c9c68d7e96070166fe385141400fa3bcb5950e

[Comment 3 Larry the Git Cow 2022-09-04 01:11:12 UTC]

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=313ec7f2df4e9ee5560f9bedd739223633e405b2

commit 313ec7f2df4e9ee5560f9bedd739223633e405b2
Author:     Sam James <[e-mail]>
AuthorDate: 2022-09-04 01:08:15 +0000
Commit:     Sam James <[e-mail]>
CommitDate: 2022-09-04 01:08:15 +0000

    sys-libs/pam: [QA] restore split-usr
    
    While split-usr support remains tenuous, dropping it from
    PAM is tantamount to removing it from Gentoo entirely and
    requires something more like a news item and a lot of
    planning.
    
    Also, really, the resultant ebuild cleanup from
    dropping it doesn't justify the gratuitous breakage:
    cost & reward.
    
    That said, I would strongly recommend at this
    point that split-usr users use an initramfs
    or actively participate in helping to solve
    split-usr bugs (see e.g. bug 443590) as at
    some point, the dam is going to break and
    maintainers may get fed up. It's already
    a barely-supported situation.
    
    Obligatory: none of this has anything
    to do with "merged /usr".
    
    Bug: https://bugs.gentoo.org/443590
    Closes: https://bugs.gentoo.org/868306
    See: 2ff9dcc3275e4f37a44eaf707fce9f53c13c2e82
    See: aeb526aa3b0875745fa0af6c754ded21af68658b
    Signed-off-by: Sam James <[e-mail]>

 sys-libs/pam/{pam-1.5.2-r1.ebuild => pam-1.5.2-r2.ebuild} | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

[Comment 4 Sam James 2024-03-03 23:03:35 UTC]

No interest in doing this at this point, as we're removing support for split-usr-without-an-initramfs. See recent news item and https://bugs.gentoo.org/398051#c8.