Precedence: list
MIME-Version: 1.0
In-Reply-To: <20170308131951.GB16013@angua.1042.ch>
References: <20170304153449.GA24485@angua.1042.ch> <20170305050829.GA28810@riseup.net>
 <CA+T2pCHF2PZE3HS6fEhoA1xJSniqdXpMjh9Uum0PpPkiUUD3ow@mail.gmail.com> <20170308131951.GB16013@angua.1042.ch>
From: William Pitcock <nenolod@dereferenced.org>
Date: Thu, 9 Mar 2017 11:28:19 -0600
Message-ID: <CA+T2pCG+1G4i-aoRHrK7-MYpRfFH-KxuxK8zU4LcUBxE0+_W_w@mail.gmail.com>
Subject: Re: [alpine-devel] Calling build() check() package() might be a bad order
To: Jean-Louis Fuchs <ganwell@fangorn.ch>
Cc: alpine-dev <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=UTF-8

Hi,

On Wed, Mar 8, 2017 at 7:19 AM, Jean-Louis Fuchs <ganwell@fangorn.ch> wrote:
> Hi William
>
> On Tue, Mar 07, 2017 at 12:34:27AM -0600, William Pitcock wrote:
>
>> I would simply not bother running the testsuite at all,
>> because you're not testing the actual binaries going into the package,
>> making the testsuite ineffective (from a distribution point of view).
>
> I think I got it, I will change my build system the following way:
>
> make check
>     Not instrumented (release mode), goal: checking compatibility
>
> make test
>     Instrumented (dev mode), goal: helping developers to find bugs
>
> Of course most of tests are shared between both test-suites, but some
> may not make sense in either test-suite.

Absolutely this is the way to go.  Then run "make check" from the APKBUILD.

William


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---