Mail archive
alpine-devel

Re: [alpine-devel] Proposal: testsuite support in APKBUILDs

From: Jakub Jirutka <jakub_at_jirutka.cz>
Date: Thu, 26 Jan 2017 14:08:29 +0100

Hi,

currently we have the following phases: sanitycheck, builddeps, clean, fetch, unpack, prepare, mkusers, rootpkg, cleanup. All of them except rootpkg are verbs. So I’d prefer “check” (as Arch) instead of “testsuite”.

Jakub

> On 26. Jan 2017, at 10:26, Timo Teras <timo.teras_at_iki.fi> wrote:
>
> On Wed, 25 Jan 2017 21:38:00 -0600
> William Pitcock <nenolod_at_dereferenced.org> wrote:
>
>> As such, I propose we add a testsuite() phase to the build process,
>> that runs after build(), but prior to package(). APKBUILDs should
>> override the testsuite phase, but the default_testsuite() function
>> will be a noop for the Alpine 3.6 release cycle that raises a warning
>> that the APKBUILD does not define any mechanism for running a
>> testsuite. If "!testsuite" is defined in $features, the warning is
>> ignored.
>>
>> For cross-builds, the testsuite would be skipped unless the package
>> is noarch.
>>
>> After Alpine 3.6 (or maybe 3.7), we change the warning to a fatal
>> error, requiring APKBUILDs to explicitly opt out of running a
>> testsuite through $features.
>>
>> Thoughts?
>
> +1
>
> We have some packages that run 'make check' or similar, but it would be
> good to make it a separate step.
>
> The above plan sounds good to me.
>
> Thanks,
> Timo
>
>
> ---
> Unsubscribe: alpine-devel+unsubscribe_at_lists.alpinelinux.org
> Help: alpine-devel+help_at_lists.alpinelinux.org
> ---
>



---
Unsubscribe:  alpine-devel+unsubscribe_at_lists.alpinelinux.org
Help:         alpine-devel+help_at_lists.alpinelinux.org
---
Received on Thu Jan 26 2017 - 14:08:29 GMT