From: Karsten Schulz <kaschu@t800.ping.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] how to test ebuilds without being root?
Date: Wed, 13 Aug 2003 08:42:15 +0200 [thread overview]
Message-ID: <200308130842.15639.kaschu@t800.ping.de> (raw)
Hi,
I wonder, how I can test my own ebuilds, without being root. As far as I can
see, there is no necessary need to work as root until the qmerge step.
At the moment, I get access violations, because as a normal user (group:
portage) I do not have write access to /var/tmp/portage/... (of course).
But I don't want to start my (maybe buggy) ebuilds as root, because my system
could become unusable by accident, if there are bugs in my ebuild.
I found the 'sandbox', 'usersandbox' and 'userpriv' things in /etc/make.conf,
but no hints, how that could help me. The section 'testing your ebuilds' in
the HOWTO does not mentions how one would really test a new ebuild on his
machine.
Do I have to setup a chroot environment for that? Or use vmware or bochs or
similar simulations? Or is there an easier and better solution?
Any hints or advices for me?
thank you very much,
Karsten
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-08-13 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 6:42 Karsten Schulz [this message]
2003-08-13 11:25 ` [gentoo-dev] how to test ebuilds without being root? Chris Gianelloni
2003-08-14 17:58 ` Karsten Schulz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308130842.15639.kaschu@t800.ping.de \
--to=kaschu@t800.ping.de \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox