Date: Tue, 30 Jun 2015 16:25:42 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: Michael Fox <415fox@gmail.com>
Cc: alpine-devel <alpine-devel@lists.alpinelinux.org>
Subject: Re: [alpine-devel] Regex compatibility
Message-ID: <20150630162542.34f46f2a@ncopa-desktop.alpinelinux.org>
In-Reply-To: <CABbL6oaVAbNBCM_3dfrA5BqTDn-f6XE2vzaDNbg0S5fPkEnYtg@mail.gmail.com>
References: <CABbL6oaVAbNBCM_3dfrA5BqTDn-f6XE2vzaDNbg0S5fPkEnYtg@mail.gmail.com>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

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


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---