public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: flameeyes@gmail.com (Diego E. 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Remember: workarounds don't warrant RESO FIXED!
Date: Thu, 20 Nov 2008 00:49:14 +0100	[thread overview]
Message-ID: <m2myfvnuo5.fsf@gmail.com> (raw)
In-Reply-To: 20081119165814.76c985a2@halo.dirtyepic.sk.ca

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

Ryan Hill <dirtyepic@gentoo.org> writes:

>> Also relevant question: some tests require root privileges. What we
>> should do in such case?
>
> When I asked this previously I was told to check the current user's
> permissions before running them.  I haven't had a case where I've had
> to though.

On libarchive there has been some tests requiring root privileges; the
temporary way out was to disable those tests, and the final way out has
been working with upstream so that the testsuite itself detects whether
you have root privileges or not and decides to skip the tests that
cannot be applied.

Just to say.

In general I think it makes sense to be able to run _most_ of the tests
as user, and discard the ones that cannot be run without root privileges
(I expect most software not to require root privileges for the tests,
it's silly to unless you need to work with file permissions or stuff
like that).

-- 
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/

[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]

      reply	other threads:[~2008-11-19 23:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 16:24 [gentoo-dev] Remember: workarounds don't warrant RESO FIXED! Diego 'Flameeyes' Pettenò
2008-11-16 16:48 ` Serkan Kaba
2008-11-16 17:42   ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-11-16 21:33 ` Ryan Hill
2008-11-17  8:52   ` Peter Volkov
2008-11-19  9:08     ` Alec Warner
2008-11-19 22:58     ` Ryan Hill
2008-11-19 23:49       ` Diego E. 'Flameeyes' Pettenò [this message]

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=m2myfvnuo5.fsf@gmail.com \
    --to=flameeyes@gmail.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