First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 64190
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Aaron Walker (RETIRED) <ka0ttic@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Ahmed Farid <afw2000@hotmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
chroot_safe-1.3.ebuild chroot_safe-1.3.ebuild text/plain Ahmed Farid 2004-09-15 16:43 0000 812 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

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

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







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

Description:   Opened: 2004-09-15 16:40 0000 
I just found that chroot_safe is a very handy app and it's be nice if it's in
portage.

you can forward all bug reports to me (or contact me on irc)

Reproducible: Always
Steps to Reproduce:
1.emerge -p chroot_safe


Actual Results:  
emerge: there are no ebuilds to satisfy "chroot_safe". 

Expected Results:  
[ebuild  N    ] app-admin/chroot_safe-1.3  0 kB

------- Comment #1 From Ahmed Farid 2004-09-15 16:43:55 0000 ------- 
Created an attachment (id=39669) [edit]
chroot_safe-1.3.ebuild

Please note that export CPPFLAGS="${CXXFLAGS}" is needed or else it'd ignore
the CXXFLAGS for building.
Also the sed line is needed because the script has a hardcoded lib path and it
must run after econf finishes.

------- Comment #2 From solar 2004-09-17 19:47:02 0000 ------- 
I don't see a point in this ebuild as app-admin/chrootuid already exists in the
tree. Reassinging to bug-wranglers

------- Comment #3 From Andreas Kobara 2004-09-18 12:01:26 0000 ------- 
chroot_safe does a runtime setup of required shared libraries, so there is no
need
to install all dependant libraries inside the chroot, as it is required with
chrootuid. You don't even need to install the binary inside the chroot, to let
it run chrooted.
In my eyes chroot_safe should be preferred over chrootuid.

------- Comment #4 From Aaron Walker (RETIRED) 2004-09-18 21:18:46 0000 ------- 
Added as app-admin/chroot_safe.  Thanks for the report.
First Last Prev Next    No search results available      Search page      Enter new bug