From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: [PATCH] unprivileged mode: generate PORTAGE_DEPCACHEDIR
Date: Mon, 10 Nov 2014 06:06:23 +0000 (UTC) [thread overview]
Message-ID: <pan$40dc7$cedc5f98$e78b7306$57912708@cox.net> (raw)
In-Reply-To: 54604CEF.2090507@gentoo.org
Zac Medico posted on Sun, 09 Nov 2014 21:28:15 -0800 as excerpted:
> The "unprivileged mode" is similar to existing prefix support. The
> "unprivileged mode" is basically useless unless your target root is
> writable. Therefore, it's a sane assumption. It won't affect you unless
> you use the new "unprivileged mode". If you do happen to use it, then
> you will probably appreciate this patch.
I misinterpreted then, thinking unprivileged mode was simply running as a
normal user.
Thanks. (And good to see you back... with more help now. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-11-10 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 23:24 [gentoo-portage-dev] [PATCH] unprivileged mode: generate PORTAGE_DEPCACHEDIR Zac Medico
2014-11-10 4:58 ` [gentoo-portage-dev] " Duncan
2014-11-10 5:28 ` Zac Medico
2014-11-10 6:06 ` Duncan [this message]
2014-11-10 11:09 ` [gentoo-portage-dev] " Alexander Berntsen
2014-11-10 18:21 ` Zac Medico
2014-11-10 20:32 ` Alexander Berntsen
2014-11-11 0:17 ` Zac Medico
2014-11-11 9:14 ` Alexander Berntsen
2014-11-15 5:19 ` Zac Medico
2014-11-15 7:21 ` [gentoo-portage-dev] [PATCH] unprivileged mode: use first_existing helper func Zac Medico
2014-11-17 8:12 ` Alexander Berntsen
2014-11-10 20:48 ` [gentoo-portage-dev] [PATCH v2] unprivileged mode: generate PORTAGE_DEPCACHEDIR Zac Medico
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='pan$40dc7$cedc5f98$e78b7306$57912708@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-portage-dev@lists.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