Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 359151

Summary: sys-kernel/module-rebuild doesn't use $PACKAGE_MANAGER and isn't cave-aware
Product: Gentoo Linux Reporter: Andreas Wiese <aw-gentoo>
Component: [OLD] Core systemAssignee: Gentoo Kernel Miscellaneous <kernel-misc>
Status: RESOLVED WONTFIX    
Severity: normal CC: christoph.diesch
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard: This package has been treecleaned, see bug #410739 for reference.
Package list:
Runtime testing required: ---
Bug Depends on: 410739    
Bug Blocks:    
Attachments: Patch for using $PACKAGE_MANAGER and cave-support.
make module-rebuild use $PACKAGE_MANAGER

Description Andreas Wiese 2011-03-16 13:00:03 UTC
sys-kernel/module-rebuild is non-portage-PM aware but doesn't use $PACKAGE_MANAGER variable set by eselect-packagemanager, what's quite annoying.  Other thing is, that module-rebuild knows how to use paludis, but isn't aware of the cave-CLI, which is by now the preferred command.  With paludis-0.60_rc1, paludis and friends will be gone in favour of the cave client.

Reproducible: Always

Steps to Reproduce:
1. »module-rebuild rebuild« with $PACKAGE_MANAGER set to paludis
2. »module-rebuild -P cave«

Actual Results:  
1. emerge
2. \|/ _____ \|/
   "@'/ , . \`@"
   /_| \___/ |_\
      \__U__/

Expected Results:  
1. paludis
2. cave

Major severity for point 2. since paludis-0.60_rc1 is expected to get into portage soon and paludis client will be gone.
Comment 1 Andreas Wiese 2011-03-16 13:00:57 UTC
Created attachment 266115 [details, diff]
Patch for using $PACKAGE_MANAGER and cave-support.
Comment 2 Andreas Wiese 2012-04-07 00:25:36 UTC
cave-issue has been resolved a long time ago, $PACKAGE_MANAGER still isn't used.  See attached patch.
Comment 3 Andreas Wiese 2012-04-07 00:26:17 UTC
Created attachment 308043 [details, diff]
make module-rebuild use $PACKAGE_MANAGER
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2013-05-26 16:18:53 UTC
*** Bug 471346 has been marked as a duplicate of this bug. ***