X-Original-To: alpine-devel@mail.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from mail.alpinelinux.org (dallas-a1.alpinelinux.org [127.0.0.1]) by mail.alpinelinux.org (Postfix) with ESMTP id B67CBDC27BB for ; Tue, 30 Jun 2015 17:12:00 +0000 (UTC) Received: from mail-oi0-f44.google.com (mail-oi0-f44.google.com [209.85.218.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 79117DC03D5 for ; Tue, 30 Jun 2015 17:12:00 +0000 (UTC) Received: by oiyy130 with SMTP id y130so12507539oiy.0 for ; Tue, 30 Jun 2015 10:11:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nSHjKvijps2pECDtEBQc5LFH3WmaRuL1SvBZqWyY9v0=; b=um6KLbwGSaw6DKjwmJCsIVunJJ11LN9/ukvtH7bVMPMoAwDAilUiti4y4QN8jIXOMt kE9sZWq2avAJOlSzlmJiEOI0v9CnUybdGx4v7MWOsftDcHWatxepWUDw58At6K7jpVgL gaVYGMv1gmJ1gmjezizsepJ+SdOGQgmRS1pyTDWtspThJgGMoOVk6metT+28UFCChqoH MV8pPubACw57crkkT9rCnk3gSqqqr5WUJMMp+NEHrrs4UkecP0Og2enGJWx2BPY/aH+C m73B+0XHa/5KYs1eN/2VdApzruerPrW6RJtOlgT2ARvfq3cKPOjUgL8+gmOvV6ZCod+I UxbQ== X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 X-Received: by 10.202.68.213 with SMTP id r204mr19833022oia.97.1435684319920; Tue, 30 Jun 2015 10:11:59 -0700 (PDT) Received: by 10.76.70.199 with HTTP; Tue, 30 Jun 2015 10:11:59 -0700 (PDT) In-Reply-To: <20150630162542.34f46f2a@ncopa-desktop.alpinelinux.org> References: <20150630162542.34f46f2a@ncopa-desktop.alpinelinux.org> Date: Tue, 30 Jun 2015 10:11:59 -0700 Message-ID: Subject: Re: [alpine-devel] Regex compatibility From: Michael Fox <415fox@gmail.com> To: Natanael Copa Cc: alpine-devel Content-Type: multipart/alternative; boundary=001a113d74eae636c20519bf4d20 X-Virus-Scanned: ClamAV using ClamSMTP --001a113d74eae636c20519bf4d20 Content-Type: text/plain; charset=UTF-8 Here's all the things I've installed to get tests to pass: gnugrep binutils diffutils coreutils linux-headers gzip bash And still, of the many basic, core packages I've tested, very few pass all tests. Maybe less than one in four. There's currently 7575 packages in alpine. How much work is that to report failing tests upstream? Even more work to try and make your own patches. Do you think we can get 200 people to take on a package each day for a month? If so, I volunteer to be one of them. On Tue, Jun 30, 2015 at 7:25 AM, Natanael Copa wrote: > On Mon, 29 Jun 2015 16:53:48 -0700 > Michael Fox <415fox@gmail.com> wrote: > > > Building software on alpine, I notice most problems stem from regex > > incompatibility. Is there some way achieve compatibility? > > yes. use portable regexes and avoid gnu (and other platform) extensions. > > > This is especially hard on `make check` because many tests involve > regexes. > > To the point that I think a lot of packagers are just not running `make > > check` because they figure the tests are failing because of test code and > > not the code under test. This may be true most of the time but it is > > allowing some bugs to slip through. > > buts in 'make check' scripts is likely slippering though yes. > > I suppose other option is to install gnu sed and gnu grep when doing > make check. But for longterm, I'd prefer upstream project think more > about portability. > > -nc > -- - Michael --001a113d74eae636c20519bf4d20 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Here's all the things I've installed to = get tests to pass:

gnugrep binutils diffutils coreutils linux-header= s gzip bash

And still, of the many basic, core packages I'= ve tested, very few pass all tests. Maybe less than one in four.

There's currently 7575 packages in alpine. How much work is that to = report failing tests upstream? Even more work to try and make your own patc= hes.

Do you think we can get 200 people to take on a package each da= y for a month? If so, I volunteer to be one of them.


On Tue, Jun 30,= 2015 at 7:25 AM, Natanael Copa <ncopa@alpinelinux.org> = wrote:
On Mon, 29 Jun 20= 15 16:53:48 -0700
Michael Fox <415fox@gmail.com>= ; wrote:

> Building software on alpine, I notice most problems stem from regex > incompatibility. Is there some way achieve compatibility?

yes. use portable regexes and avoid gnu (and other platform) extensi= ons.

> This is especially hard on `make check` because many tests involve reg= exes.
> To the point that I think a lot of packagers are just not running `mak= e
> check` because they figure the tests are failing because of test code = and
> not the code under test. This may be true most of the time but it is > allowing some bugs to slip through.

buts in 'make check' scripts is likely slippering though yes= .

I suppose other option is to install gnu sed and gnu grep when doing
make check. But for longterm, I'd prefer upstream project think more about portability.

-nc



--

-
Michael
--001a113d74eae636c20519bf4d20-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---