[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: make test-baseline fails
From: |
Dan Eble |
Subject: |
Re: make test-baseline fails |
Date: |
Sat, 7 Dec 2019 11:25:37 -0500 |
On Dec 7, 2019, at 05:43, James <address@hidden> wrote:
>
> So apart from 'required' things breaking as newer versions come out (e.g
> Ghostscript), should I be testing patches with required AND non-required
> components installed? Or should I be testing them with ONLY required
> components but then we should make patchy-staging use required AND
> non-required?
>
> Else we get into a mess with who has what on which system they happen to be
> building from.
My 5¢ (no more pennies here):
It's enough to test with or without tidy, whichever happens to be the condition
of your system.
It would be nice if patchy-staging used tidy, but it isn't a high priority.
It is wise for a contributor making changes to output-distance.py to install
tidy.
—
Dan
- Re: make test-baseline fails, (continued)
- Re: make test-baseline fails, Thomas Morley, 2019/12/06
- Re: make test-baseline fails, Dan Eble, 2019/12/06
- Re: make test-baseline fails, Thomas Morley, 2019/12/06
- Re: make test-baseline fails, Dan Eble, 2019/12/06
- Re: make test-baseline fails, Thomas Morley, 2019/12/06
- Re: make test-baseline fails, Dan Eble, 2019/12/06
- Re: make test-baseline fails, Thomas Morley, 2019/12/07
- Re: make test-baseline fails, James, 2019/12/07
- Re: make test-baseline fails, Thomas Morley, 2019/12/07
- Re: make test-baseline fails, James, 2019/12/07
- Re: make test-baseline fails,
Dan Eble <=
- Re: make test-baseline fails, Dan Eble, 2019/12/07