| 1 |
On Fri, Aug 24, 2018 at 9:23 AM Kent Fredric <kentnl@g.o> wrote: |
| 2 |
> |
| 3 |
> On Tue, 21 Aug 2018 22:29:29 -0400 |
| 4 |
> Mike Gilbert <floppym@g.o> wrote: |
| 5 |
> |
| 6 |
> > Setting RESTRICT="!test? ( test )" is generally sufficient. |
| 7 |
> |
| 8 |
> But that would require setting that virtually *everything* that has |
| 9 |
> both tests, and required dependencies for tests. |
| 10 |
> |
| 11 |
> Which, in my experience, is practically everything with tests. |
| 12 |
> |
| 13 |
> To the point it seems like that should be the *default* mechanic, not a |
| 14 |
> requirement that everyone pay not to have a randomly broken package. |
| 15 |
|
| 16 |
If you want to define behavior that can be relied upon in ebuilds, it |
| 17 |
should be specified in PMS. PMS does not define any meaning for the |
| 18 |
"test" USE flag. |
Archives