| 1 |
On Thu, 23 Mar 2017 18:46:35 +0000 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Thu, 23 Mar 2017 19:41:01 +0100 |
| 5 |
> Alexis Ballier <aballier@g.o> wrote: |
| 6 |
> > > The PMS[0] says |
| 7 |
> > > |
| 8 |
> > > Ebuilds must not access [FILESDIR] in global scope. |
| 9 |
> > > |
| 10 |
> > > But, for example, autoconf-2.69-r2.ebuild does, |
| 11 |
> > > |
| 12 |
> > > if [[ -z ${__EBLITS__} && -n ${FILESDIR} ]] ; then |
| 13 |
> > > source "${FILESDIR}"/eblits/main.eblit || die |
| 14 |
> > > fi |
| 15 |
> > > |
| 16 |
> > > in global scope. |
| 17 |
> > > |
| 18 |
> > |
| 19 |
> > Continuing to be the devil's advocate, it seems adding '&& -d |
| 20 |
> > ${FILESDIR}' to that if would fix the issue too. At least with all |
| 21 |
> > currently approved EAPIs. |
| 22 |
> |
| 23 |
> Please stop. PMS was not written with the kind of resources needed to |
| 24 |
> deal with people deliberately trying to find loopholes. |
| 25 |
> |
| 26 |
|
| 27 |
Yep, nor should it be that way. However, retroactively adding new |
| 28 |
rules, pushing patches to package managers to enforce the "cleaner" |
| 29 |
behavior, coming with a QA hammer and useless deadlines with poor |
| 30 |
explanations, rewriting the libc ebuilds and proposing to push these |
| 31 |
straight to stable next week starts to resemble more to a pissing |
| 32 |
context than a will to have a sane discussion. |
Archives