1 |
On Thu, Aug 15, 2019 at 8:33 AM Michael Orlitzky <mjo@g.o> wrote: |
2 |
> |
3 |
> On 8/15/19 3:19 AM, Ulrich Mueller wrote: |
4 |
> > |
5 |
> > I don't think that's a sane situation, so maybe the eclass should just |
6 |
> > die here? (Basically, there are two possibilities: Either, things will |
7 |
> > break if the dir is missing, then dying might be the best option. |
8 |
> > Or, everything works without the dir, then the ebuild should set it to |
9 |
> > /dev/null, in the first place.) |
10 |
> > |
11 |
> |
12 |
> That's my feeling as well. In 100% of cases so far, this has been a |
13 |
> useful QA tool. Can we wait until that's not the case to change it? |
14 |
|
15 |
I think an explicit die with a useful error message for the user would |
16 |
be better than the status-quo. |