From: "Rob Cakebread" <robc@myrealbox.com>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Too root or not to root?
Date: Thu, 21 Aug 2003 16:39:15 -0700 [thread overview]
Message-ID: <1061509155.af5a4dc0robc@myrealbox.com> (raw)
Hi,
I've written an editor/IDE for creating ebuilds (http://abeni.sf.net).
It requires the user to run it as root. In previous versions it ran as
a regular user and executed commands such as emerge and ebuild with sudo.
This worked ok but I had to do a lot of silly things because regular users
don't have read permissions below $WORKDIR. My app will open the configure
and Makefile automatically when you click the 'unpack' icon, for instance,
but I had to do some really kludgey things to check if the configure/Makefile
existed in ${S}. Then to read it I had to copy it to the /tmp dir with sudo
then read it in as regular user.
Is there a good reason that $WORKDIR isn't world readable? Should I just not
worry about it and continue requiring everyone run as root?
I notice other portage GUIs I've seen all require the user to run as root,
such as kportage, portagemaster etc, so maybe I shouldn't be concerned.
P.S.
Does anyone know of a Bash script beautifier? Mainly I need to convert spaces
to tabs in ebuilds and I'd rather use an external program if one exists.
Thanks,
Rob
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-08-21 23:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 23:39 Rob Cakebread [this message]
2003-08-21 23:54 ` [gentoo-dev] Too root or not to root? Mike Frysinger
2003-08-22 2:26 ` Georgi Georgiev
2003-08-22 8:10 ` Mamoru KOMACHI
-- strict thread matches above, loose matches on Subject: below --
2003-08-22 0:14 Rob Cakebread
2003-08-22 0:22 ` Mike Frysinger
2003-08-22 1:16 ` Alec Berryman
2003-08-22 8:10 ` Sven Vermeulen
2003-08-22 8:47 ` Paul de Vrieze
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=1061509155.af5a4dc0robc@myrealbox.com \
--to=robc@myrealbox.com \
--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