From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [PATCH] sys-devel/autoconf: Convert from eblits into an eclass, #586424
Date: Thu, 23 Mar 2017 18:46:35 +0000 [thread overview]
Message-ID: <20170323184635.3233779f@snowblower> (raw)
In-Reply-To: <20170323194101.0e6af3c2@gentoo.org>
On Thu, 23 Mar 2017 19:41:01 +0100
Alexis Ballier <aballier@gentoo.org> wrote:
> > The PMS[0] says
> >
> > Ebuilds must not access [FILESDIR] in global scope.
> >
> > But, for example, autoconf-2.69-r2.ebuild does,
> >
> > if [[ -z ${__EBLITS__} && -n ${FILESDIR} ]] ; then
> > source "${FILESDIR}"/eblits/main.eblit || die
> > fi
> >
> > in global scope.
> >
>
> Continuing to be the devil's advocate, it seems adding '&& -d
> ${FILESDIR}' to that if would fix the issue too. At least with all
> currently approved EAPIs.
Please stop. PMS was not written with the kind of resources needed to
deal with people deliberately trying to find loopholes.
--
Ciaran McCreesh
next prev parent reply other threads:[~2017-03-23 18:46 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 9:38 [gentoo-dev] [PATCH] sys-devel/autoconf: Convert from eblits into an eclass, #586424 Michał Górny
2017-03-16 10:07 ` Ulrich Mueller
2017-03-16 12:19 ` Alexis Ballier
2017-03-16 12:57 ` Ulrich Mueller
2017-03-16 18:42 ` Alexis Ballier
2017-03-16 18:58 ` Michał Górny
2017-03-16 22:48 ` Alexis Ballier
2017-03-16 20:14 ` Ulrich Mueller
2017-03-16 23:12 ` Alexis Ballier
2017-03-16 12:15 ` Alexis Ballier
2017-03-16 12:59 ` Michał Górny
2017-03-16 13:30 ` [gentoo-dev] [PATCH v2] " Michał Górny
2017-03-20 8:35 ` [gentoo-dev] Re: [PATCH] " Mike Frysinger
2017-03-20 9:49 ` Ulrich Mueller
2017-03-20 11:19 ` Alexis Ballier
2017-03-20 14:12 ` Ulrich Mueller
2017-03-20 17:01 ` Alexis Ballier
2017-03-20 17:40 ` Mike Gilbert
2017-03-20 18:15 ` Alexis Ballier
2017-03-20 18:26 ` Mike Gilbert
2017-03-20 18:24 ` Michał Górny
2017-03-20 21:12 ` Alexis Ballier
2017-03-20 21:19 ` Michał Górny
2017-03-20 21:30 ` Alexis Ballier
2017-03-20 19:25 ` Ulrich Mueller
2017-03-20 21:14 ` Alexis Ballier
2017-03-21 8:28 ` Joshua Kinard
2017-03-21 8:43 ` Kristian Fiskerstrand
2017-03-21 9:17 ` Alexis Ballier
2017-03-21 9:41 ` Kristian Fiskerstrand
2017-03-21 10:00 ` Alexis Ballier
2017-03-21 10:16 ` Kristian Fiskerstrand
2017-03-21 21:54 ` Joshua Kinard
2017-03-21 10:24 ` Andreas K. Huettel
2017-03-23 9:41 ` Andreas K. Huettel
2017-03-23 9:51 ` Alexis Ballier
2017-03-23 10:55 ` Andreas K. Huettel
2017-03-23 13:36 ` Alexis Ballier
2017-03-23 16:36 ` Michael Orlitzky
2017-03-23 18:41 ` Alexis Ballier
2017-03-23 18:46 ` Ciaran McCreesh [this message]
2017-03-23 19:12 ` Alexis Ballier
2017-03-23 19:17 ` Ciaran McCreesh
2017-03-23 19:49 ` Alexis Ballier
2017-03-23 19:53 ` Ciaran McCreesh
2017-03-23 16:53 ` Michał Górny
2017-03-23 18:52 ` Alexis Ballier
2017-03-23 19:00 ` Ciaran McCreesh
2017-03-23 19:00 ` Michał Górny
2017-03-23 20:22 ` Alexis Ballier
2017-03-23 20:30 ` Ciaran McCreesh
2017-03-23 21:37 ` Alexis Ballier
2017-03-23 21:45 ` Ciaran McCreesh
2017-03-24 10:23 ` Alexis Ballier
2017-03-23 21:20 ` Michael Orlitzky
2017-03-23 21:42 ` Alexis Ballier
2017-03-23 21:45 ` David Seifert
2017-03-24 8:57 ` Alexis Ballier
2017-03-24 10:05 ` Ulrich Mueller
2017-03-24 10:36 ` Alexis Ballier
2017-03-24 1:58 ` M. J. Everitt
2017-03-24 19:43 ` [gentoo-dev] " Michał Górny
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=20170323184635.3233779f@snowblower \
--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