From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] root:root and fbsd
Date: Sun, 22 May 2005 10:49:39 +0200 [thread overview]
Message-ID: <200505221049.39924@enterprise.flameeyes.is-a-geek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Hi,
ok another problem for Gentoo/FreeBSD project :P
Currently there are a few places where, to fix permissions of files, the
ebuilds does a chown -R root:root ${D} or something similar.
Unfortunately such a command is invalid on G/FBSD because there's no root
group, instead wheel group has GID=0.
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...
Comments?
--
Diego "Flameeyes" Pettenò
Gentoo Developer (Gentoo/FreeBSD, Video, Gentoo/AMD64)
http://dev.gentoo.org/~flameeyes/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-05-22 8:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 8:49 Diego 'Flameeyes' Pettenò [this message]
2005-05-22 9:06 ` [gentoo-dev] root:root and fbsd 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
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=200505221049.39924@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@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