From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Francesco Riosa <vivo75@gmail.com>,
Mike Gilbert <floppym@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] use.desc: Improve description of USE=test
Date: Fri, 24 Aug 2018 16:45:04 -0700 [thread overview]
Message-ID: <670d034e-c081-46f9-8948-de12d44b50f0@gentoo.org> (raw)
In-Reply-To: <9d0b7e10-1e81-f04c-8489-db03cdc60886@gmail.com>
On 08/24/2018 04:14 PM, Francesco Riosa wrote:
>
> Il 24/08/18 19:08, Mike Gilbert ha scritto:
>> On Fri, Aug 24, 2018 at 10:45 AM Kent Fredric <kentnl@gentoo.org> wrote:
>>> On Fri, 24 Aug 2018 10:27:01 -0400
>>> Mike Gilbert <floppym@gentoo.org> wrote:
>>>
>>>> If you want to define behavior that can be relied upon in ebuilds, it
>>>> should be specified in PMS. PMS does not define any meaning for the
>>>> "test" USE flag.
>>> We should eschew idealism about how the world *should* behave, and avoid
>>> making portage a steaming garbage heap in order to comply with a
>>> terrible PMS specification of a heavily used feature.
>> Portage still works just fine for most people who would enable
>> FEATURES=test. Stop exaggerating.
>>
> People enabling FEATURES=test on most but not all packages had some
> troubles and they need to disable them in both package.{env,use}
> I'd like to have a flag to reinstate the previous portage behaviour, but
> that's probably too late
Would a FEATURES setting that implies RESTRICT="!test? ( test )" for all
ebuilds do what you want?
--
Thanks,
Zac
next prev parent reply other threads:[~2018-08-24 23:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 14:34 [gentoo-dev] [PATCH] use.desc: Improve description of USE=test Michał Górny
2018-08-20 14:57 ` Mike Gilbert
2018-08-20 14:59 ` Michał Górny
2018-08-21 5:54 ` Davide Pesavento
2018-08-21 6:46 ` Michał Górny
2018-08-21 15:57 ` Davide Pesavento
2018-08-21 16:02 ` Davide Pesavento
2018-08-21 16:23 ` Michał Górny
2018-08-22 1:21 ` Thomas Deutschmann
2018-08-22 2:29 ` Mike Gilbert
2018-08-24 13:23 ` Kent Fredric
2018-08-24 14:27 ` Mike Gilbert
2018-08-24 14:37 ` Virgil Dupras
2018-08-24 17:07 ` Mike Gilbert
2018-08-24 14:45 ` Kent Fredric
2018-08-24 17:08 ` Mike Gilbert
2018-08-24 23:14 ` Francesco Riosa
2018-08-24 23:45 ` Zac Medico [this message]
2018-08-24 23:56 ` Francesco Riosa
2018-08-26 7:14 ` Zac Medico
2018-08-26 7:21 ` Zac Medico
2018-08-25 1:18 ` Michał Górny
2018-08-25 11:48 ` Jeroen Roovers
2018-08-21 20:06 ` Juippisi .
2018-08-21 20:18 ` Kristian Fiskerstrand
2018-08-22 1:11 ` Thomas Deutschmann
2018-08-21 6:54 ` [gentoo-dev] [PATCH v3] " 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=670d034e-c081-46f9-8948-de12d44b50f0@gentoo.org \
--to=zmedico@gentoo.org \
--cc=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vivo75@gmail.com \
/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