From: Grant Goodyear <g2boojum@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] root:root and fbsd
Date: Mon, 23 May 2005 11:23:44 -0500 [thread overview]
Message-ID: <20050523162344.GF14128@bmb24.uth.tmc.edu> (raw)
In-Reply-To: <200505221049.39924@enterprise.flameeyes.is-a-geek.org>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
Diego 'Flameeyes' Pettenò wrote: [Sun May 22 2005, 03:49:39AM CDT]
> So I was wondering for a solution for this problem: we have a
> $USERLAND variable which can be used to select the way the chown must
> be done, if chown root:root or chown root:wheel; I think both BSD and
> Darwin userland prefers root:wheel above root:root, so maybe adding a
> function in eutils which fixes the permissions based on the current
> $USERLAND value is enough...
Of course, this issue is precisely what GLEP 27 was created to handle.
The portage devs have let us know that xml is a problem, but otherwise
this GLEP appears sound, and I believe that the portage team has
something along these lines as part of their long-range plans.
-g2boojum-
--
Grant Goodyear
Gentoo Developer
g2boojum@gentoo.org
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0 9573 A6DC 7152 E0F6 5B76
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-23 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 8:49 [gentoo-dev] root:root and fbsd Diego 'Flameeyes' Pettenò
2005-05-22 9:06 ` Ciaran McCreesh
2005-05-22 9:20 ` Diego 'Flameeyes' Pettenò
2005-05-22 15:04 ` Kito
2005-05-22 11:27 ` Mike Frysinger
2005-05-22 9:09 ` Stuart Longland
2005-05-24 20:26 ` Diego 'Flameeyes' Pettenò
2005-05-24 21:51 ` Mike Frysinger
2005-05-22 14:38 ` Alec Warner
2005-05-22 14:48 ` Diego 'Flameeyes' Pettenò
2005-05-23 16:23 ` Grant Goodyear [this message]
2005-05-23 17:22 ` Mike Frysinger
2005-05-25 10:12 ` 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=20050523162344.GF14128@bmb24.uth.tmc.edu \
--to=g2boojum@gentoo.org \
--cc=gentoo-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