1 |
On Wed, 2003-08-13 at 02:42, Karsten Schulz wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I wonder, how I can test my own ebuilds, without being root. As far as I can |
5 |
> see, there is no necessary need to work as root until the qmerge step. |
6 |
> |
7 |
> At the moment, I get access violations, because as a normal user (group: |
8 |
> portage) I do not have write access to /var/tmp/portage/... (of course). |
9 |
> But I don't want to start my (maybe buggy) ebuilds as root, because my system |
10 |
> could become unusable by accident, if there are bugs in my ebuild. |
11 |
|
12 |
You could try using su to become user portage and working form there, or |
13 |
you can change permissions on /var/tmp/portage. Personally, I do all |
14 |
ebuild testing as first root using no FEATURES, then add them one by one |
15 |
until I have them all tested. |
16 |
|
17 |
I find that a combination of sandbox and userpriv keep your system from |
18 |
being hosed in the case of a bad ebuild. These ensure that root |
19 |
privileges are dropped for the unpack and compile parts of the ebuild |
20 |
and that nothing is done on your live filesystem until the qmerge, which |
21 |
requires root. |
22 |
|
23 |
> I found the 'sandbox', 'usersandbox' and 'userpriv' things in /etc/make.conf, |
24 |
> but no hints, how that could help me. The section 'testing your ebuilds' in |
25 |
> the HOWTO does not mentions how one would really test a new ebuild on his |
26 |
> machine. |
27 |
> |
28 |
> Do I have to setup a chroot environment for that? Or use vmware or bochs or |
29 |
> similar simulations? Or is there an easier and better solution? |
30 |
|
31 |
I live dangerously and use my live system. There is very little that |
32 |
you can totally muck up that will bring your system to its knees. Of |
33 |
course, you can also make a backup before doing anything you deem |
34 |
dangerous enough to mess up your system. |
35 |
|
36 |
-- |
37 |
Chris Gianelloni |
38 |
Developer, Gentoo Linux |