From: Dan Meltzer <parallelgrapefruit@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on
Date: Mon, 26 Dec 2005 09:44:26 -0500 [thread overview]
Message-ID: <46059ce10512260644q3223f726ve1c831aba6ec8020@mail.gmail.com> (raw)
In-Reply-To: <46059ce10512260632r40e5650as8b62513b220bce28@mail.gmail.com>
and my bad.
I am not yet awake.
It died cause of runpaths on strict, it just showed both, and I wasn't
thinking when I sent earlier email...
On 12/26/05, Dan Meltzer <parallelgrapefruit@gmail.com> wrote:
> On 12/26/05, Diego 'Flameeyes' Pettenò <flameeyes@gentoo.org> wrote:
> > On Monday 26 December 2005 13:59, Simon Stelling wrote:
> > > > Actually "stricter", and there are way too many people to put that in
> > > > without knowing what that do... or is it a default nowadays, I'm not even
> > > > sure.
> > > You're mixing up 'strict' with 'stricter'.
> > Well if I'm mixing up, someone moved the QA checks from stricter to strict
> > lately ;)
> > I don't run strict as I usually have modified ebuilds if I'm working on them;
> > I don't run stricter as lot of packages that fails are not mine, I usually
> > use it only when I'm testing my packages or my changes.
>
> strict is in make.defaults...
> This causes packages with executable stacks to die, and fairly
> arbitrarily imo (with portage 2.1_pre2 that is) (see bug 116611).
>
> IMUO, portage should never die when an issue of questionable merit
> comes up and features are simply those set by default.
>
>
> >
> > --
> > Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/
> > Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
> >
> >
> >
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-26 14:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 23:32 [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on Petteri Räty
2005-12-26 0:13 ` Jason Stubbs
2005-12-26 11:01 ` Jakub Moc
2005-12-26 12:53 ` Petteri Räty
2005-12-26 12:58 ` Danny van Dyk
2005-12-26 13:28 ` Jason Stubbs
2005-12-26 13:53 ` Re[2]: " Jakub Moc
2005-12-26 1:26 ` Diego 'Flameeyes' Pettenò
2005-12-26 2:28 ` Chris White
2005-12-26 12:04 ` Diego 'Flameeyes' Pettenò
2005-12-26 12:44 ` Petteri Räty
2005-12-26 12:59 ` Simon Stelling
2005-12-26 14:14 ` Diego 'Flameeyes' Pettenò
2005-12-26 14:32 ` Dan Meltzer
2005-12-26 14:44 ` Dan Meltzer [this message]
2005-12-27 19:41 ` [gentoo-dev] Putting qa warnings to a text file instead of showing them to the world Petteri Räty
2005-12-27 19:58 ` Mike Frysinger
2005-12-27 20:02 ` Lares Moreau
2005-12-27 20:10 ` Petteri Räty
2005-12-27 20:22 ` Lares Moreau
2005-12-28 1:34 ` Kalin KOZHUHAROV
2005-12-28 1:53 ` Lares Moreau
2005-12-28 2:03 ` Kalin KOZHUHAROV
2005-12-28 3:21 ` Ryan Tandy
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=46059ce10512260644q3223f726ve1c831aba6ec8020@mail.gmail.com \
--to=parallelgrapefruit@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