public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Patrick Lauer <patrick@gentoo.org>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/zzuf: ChangeLog zzuf-0.13.ebuild
Date: Sat, 27 Feb 2010 00:52:56 +0200	[thread overview]
Message-ID: <4B8850C8.8020607@gentoo.org> (raw)
In-Reply-To: <4B884FC0.5090205@gentoo.org>

On 02/27/2010 12:48 AM, Patrick Lauer wrote:
> On 02/26/10 22:02, Samuli Suominen wrote:
>> On 02/26/2010 10:50 PM, Patrick Lauer (patrick) wrote:
> 
>>> src_test() {
>>> 	if hasq sandbox ${FEATURES}; then
>>> 		ewarn "zzuf tests don't work correctly when sandbox is enabled,"
>>> 		ewarn "skipping tests. If you want to run the testsuite, please"
>>> 		ewarn "disable sandbox for this build."
>>> 		return
>>> 	fi
>>
>> Testing FEATURES from ebuild? You shouldn't do that.
> 
> I disagree. That's a good way not to fail there, unless someone has a
> better idea how to make that work.
> 
> And I'd appreciate it if PMS would stop refusing to document FEATURES.
> (Double negative? I mean: PMS should document reality)
> 
> I won't mind if someone "fixes" that in a way that still has the same
> functionality, but I honestly don't see it as a bug, so I'll leave it as
> it is.
> 

http://bugs.gentoo.org/show_bug.cgi?id=279465
http://bugs.gentoo.org/show_bug.cgi?id=174335

Even this is better,

RESTRICT="test" # Doesn't work with sandbox enabled, see bug 279465

My point is simple: If you don't like the situation / policy, try to
change it, don't go solo with singular ebuild.



  reply	other threads:[~2010-02-26 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Nl78n-00084u-L7@stork.gentoo.org>
2010-02-26 21:02 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/zzuf: ChangeLog zzuf-0.13.ebuild Samuli Suominen
2010-02-26 22:48   ` Patrick Lauer
2010-02-26 22:52     ` Samuli Suominen [this message]
2010-02-27  8:31     ` 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=4B8850C8.8020607@gentoo.org \
    --to=ssuominen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=patrick@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