public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: Remaining PMS todo list etc
Date: Fri, 21 Mar 2008 07:54:26 +0000	[thread overview]
Message-ID: <20080321075426.54db71b1@googlemail.com> (raw)
In-Reply-To: <frutuo$dnd$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Thu, 20 Mar 2008 18:02:31 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:
> > How about just checking EUID == 0 in src_test and skip the tests
> > (with a ewarn message) if it doesn't match your needs?
> 
> I thought I remembered someone raising a stink about checking
> permissions being a race condition because the condition can change
> between the checking and performing the action.  Maybe that was only
> about write permissions...

That's in cases like if [[ -w foo ]] ; then blah foo ; fi . Checking a
variable that's constant for the phase is not racy.

> If checking EUID is an acceptable method,
> it should be relatively simple to write an eclass to handle the
> common cases and have ebuilds use that instead of checking $FEATURES
> (which i do think is a bug).

Does it really need an eclass for something so simple?

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-03-21  8:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 18:27 [gentoo-dev] Remaining PMS todo list etc Ciaran McCreesh
2008-03-20  0:32 ` [gentoo-dev] " Ryan Hill
2008-03-20  3:45   ` Marius Mauch
2008-03-21  0:02     ` Ryan Hill
2008-03-21  7:54       ` Ciaran McCreesh [this message]
2008-03-21 18:17         ` Ryan Hill
2008-03-20  7:41   ` Ciaran McCreesh
2008-03-20  7:52     ` Christian Faulhammer
2008-03-20  7:55       ` Ciaran McCreesh
2008-03-21 11:47         ` Christian Faulhammer
2008-03-21 11:52           ` Ciaran McCreesh

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=20080321075426.54db71b1@googlemail.com \
    --to=ciaran.mccreesh@googlemail.com \
    --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