Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 31748
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Chris PeBenito <pebenito@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
ebuild.sh-dyn_preinst.diff ebuild.sh-dyn_preinst.diff patch Chris PeBenito 2003-10-22 09:34 0000 2.86 KB Details | Diff
ebuild.sh-dyn_preinst.diff updated dyn_preinst patch patch Chris PeBenito 2003-11-11 11:52 0000 3.17 KB Details | Diff
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 31748 depends on: Show dependency tree
Bug 31748 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-10-22 09:31 0000 
Here's a patch against ebuild.sh that adds dyn_preinst, and moves the sfperms
and selinux blocks from dyn_install to dyn_preinst.  It is dependant on the
${EMERGE_FROM} being set (binary or ebuild), which is a change you said would
be made.  Please note the last hunk of the patch; I'm not sure which case you
want preinst moved to.

------- Comment #1 From Chris PeBenito 2003-10-22 09:34:35 0000 ------- 
Created an attachment (id=19623) [details]
ebuild.sh-dyn_preinst.diff

patch against ebuild.sh from portage-2.0.49-r15 (cvs v1.143)

------- Comment #2 From Chris PeBenito 2003-11-11 11:52:41 0000 ------- 
Created an attachment (id=20605) [details]
updated dyn_preinst patch

This updated one adds in FEATURES nodoc, noman, and noinfo to remove the
respective stuff from /usr/share, as needed by the embedded team

------- Comment #3 From Chris PeBenito 2003-11-11 12:37:39 0000 ------- 
Ok, genome tells me that the FEATURES in the 2nd patch will be covered by
the forthcoming INSTALL_PROTECT.  So, ignore the 2nd patch, and just look
at the first patch.

------- Comment #4 From Nicholas Jones (RETIRED) 2003-11-11 18:31:04 0000 ------- 
Went with patch 2.
in for -r17
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug