[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43746: What to do about packages that don't support --without-tests
|
From: |
pelzflorian (Florian Pelz) |
|
Subject: |
bug#43746: What to do about packages that don't support --without-tests / #:tests? #f setting |
|
Date: |
Sat, 3 Oct 2020 00:48:21 +0200 |
On Thu, Oct 01, 2020 at 11:07:54PM +0200, Ludovic Courtès wrote:
> Oh, we should fix ‘glib’ in ‘core-updates’.
I verified the attached patch fixes glib on the ‘master’ branch. I’m
not sure about adding a copyright. Anyway. Shall I push it to
‘core-updates’ or wait until I can test it on ‘core-updates’ without
rebuilding the world?
> I’m inclined to apply the patch you propose and leaving phases
> unchanged.
> […]
> I’d change the last sentence to:
>
> Therefore, @option{--without-tests} has no effect on these packages.
I changed it and pushed the patch to the documentation as
3c01fcc1bb9c086f487d9694cb91a57d7abd0880. Thank you!
(I maybe should have written in the commit message “Fixes
<https://bugs.gnu.org/43746>.” Oh well. I will leave the bug open
though because glib is not fixed yet.)
Regards,
Florian
0001-gnu-glib-Adhere-to-without-tests-option.patch
Description: Text document