From nobody Thu Mar 28 23:29:54 2024 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 E3EA1DC03D5 for ; Mon, 29 Jun 2015 23:53:48 +0000 (UTC) Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id C9172DC0229 for ; Mon, 29 Jun 2015 23:53:48 +0000 (UTC) Received: by oigx81 with SMTP id x81so129610187oig.1 for ; Mon, 29 Jun 2015 16:53:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=w3rcEGtFW+CIJzBM2Df7MjnvNrZ/IR6cIlXpxuOswDU=; b=hyHNIMAOvbJHAIrL+6KSr17Rk8HkOWCwtLfcGOJYKdiBchpTY0pP/LY8D7nwe3xnbG N5u5hxyVAYEsakJuDW6BxeNkb9ctXbpL5BA3sKn7ecoLl0KZyXpT5KgbAsd/4v6pAy0H mSR3LJCEtugdZDcpBgYs58MN571rYEKJGLNjvZ+7QtML5M2GJQAhfEEl8Vh1gndoT7x3 d2ELE2Cd5fPJ73Y9sDYvRX+4a1YQHdPMQ3zjUFqnEVIH+dcofABdFrMixM5hgIU66C5k KBQ5+mm764Fj1xW0Gj502yjdfD5BPnjjimM8CqjZc4txEI2Uc6RsV6MQTK56Hs9TCRza +CDw== 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 r204mr15888105oia.97.1435622028240; Mon, 29 Jun 2015 16:53:48 -0700 (PDT) Received: by 10.76.70.199 with HTTP; Mon, 29 Jun 2015 16:53:48 -0700 (PDT) Date: Mon, 29 Jun 2015 16:53:48 -0700 Message-ID: Subject: [alpine-devel] Regex compatibility From: Michael Fox <415fox@gmail.com> To: alpine-devel Content-Type: multipart/alternative; boundary=001a113d74ea066f2b0519b0cdeb X-Virus-Scanned: ClamAV using ClamSMTP --001a113d74ea066f2b0519b0cdeb Content-Type: text/plain; charset=UTF-8 Building software on alpine, I notice most problems stem from regex incompatibility. Is there some way achieve compatibility? 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. -- - Michael --001a113d74ea066f2b0519b0cdeb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Building software on alpine, I notice most problems s= tem from regex incompatibility. Is there some way achieve compatibility?
This is especially hard on `make check` because many tests invol= ve regexes. To the point that I think a lot of packagers are just not runni= ng `make check` because they figure the tests are failing because of test c= ode and not the code under test. This may be true most of the time but it i= s allowing some bugs to slip through.

--

-
Michael
--001a113d74ea066f2b0519b0cdeb-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org --- From nobody Thu Mar 28 23:29:54 2024 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 A502FDC6ACC for ; Tue, 30 Jun 2015 13:05:04 +0000 (UTC) Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 6936BDC6ACB for ; Tue, 30 Jun 2015 13:05:03 +0000 (UTC) Received: by ieqy10 with SMTP id y10so11662166ieq.0 for ; Tue, 30 Jun 2015 06:05:02 -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=dOBjW2Op2YvKzfkJChDFdKrZTbYXu5ZTgGHAsTLMwck=; b=i5pi5Q76fBkHpdckWkhKUUPQT/Q50zYgEFfeUWfG7GTJqKu4ziFMDlqg69rCL8Xp96 PSGnTliZb+l/gbtQdZc3yJ1MSDvg4eRJxwTF3xRQzRwfVr+c1ZSMQrgKFbjjocSNkdVi fF+7Ce/BgDRBIsKjtI8L15k2c0uhTBlX3JixuA/JZDxqekxu08QSfOfppNYx4/ZwWNaY v1gtOOchCF1phR4dm+xwyuk9Kp/92xYmpEkd/oe+AjrYL7+4npILD6skxSwLPJ/hbOG0 rZaKBe57UofsJfT3BNqPU9Xdz1q3gSFt/opq8BD6/s0+VjsiTBRc7lEppXUkxHqiS0og nQ7w== 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.107.151.75 with SMTP id z72mr27277017iod.46.1435669502486; Tue, 30 Jun 2015 06:05:02 -0700 (PDT) Received: by 10.36.137.84 with HTTP; Tue, 30 Jun 2015 06:05:02 -0700 (PDT) In-Reply-To: References: Date: Tue, 30 Jun 2015 08:05:02 -0500 Message-ID: Subject: Re: [alpine-devel] Regex compatibility From: Jeff Pohlmeyer To: Michael Fox <415fox@gmail.com> Cc: alpine-devel Content-Type: text/plain; charset=UTF-8 X-Virus-Scanned: ClamAV using ClamSMTP On Mon, Jun 29, 2015 at 6:53 PM, Michael Fox <415fox@gmail.com> wrote: > Building software on alpine, I notice most problems stem from regex > incompatibility. Is there some way achieve compatibility? > > This is especially hard on `make check` because many tests involve regexes. If it's a matter of the tests actually depending on regex library calls, I would say that's something that would probably need to be fixed in the test, since not all C libraries are going to have the same implementation. But if the tests are depending on the behavior of the "grep" command, the fix might be as simple as ensuring that the test environment has GNU grep installed in the path ahead of busybox grep. (since GUN grep uses PCRE rather than MUSL for its regex.) - Jeff --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org --- From nobody Thu Mar 28 23:29:54 2024 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 A6798DC181D; Tue, 30 Jun 2015 14:25:46 +0000 (UTC) Received: from ncopa-desktop.alpinelinux.org (unknown [79.160.13.133]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: n@tanael.org) by mail.alpinelinux.org (Postfix) with ESMTPSA id E2ABFDC0D4D; Tue, 30 Jun 2015 14:25:45 +0000 (UTC) Date: Tue, 30 Jun 2015 16:25:42 +0200 From: Natanael Copa To: Michael Fox <415fox@gmail.com> Cc: alpine-devel Subject: Re: [alpine-devel] Regex compatibility Message-ID: <20150630162542.34f46f2a@ncopa-desktop.alpinelinux.org> In-Reply-To: References: X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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 --- From nobody Thu Mar 28 23:29:54 2024 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 --- From nobody Thu Mar 28 23:29:54 2024 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 1D785DCCD77 for ; Tue, 30 Jun 2015 18:12:18 +0000 (UTC) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id D2D98DC6A85 for ; Tue, 30 Jun 2015 18:12:17 +0000 (UTC) Received: by oigx81 with SMTP id x81so13771249oig.1 for ; Tue, 30 Jun 2015 11:12:17 -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=fIDDbVMx+fzMR7IrO4QBxjCsg+0w57SA2Ihs7yjyQU0=; b=U26A5E+oxSRn9H/3lrqtlS+hjwVo62elPzOHQZjkWmjB5Y2GM4luulMLqMU19TitPC M1drR1oINgEDQXL3rn0joCAwpSZjE8mIuQGGdOF/7aJgqlLiD+q+UnqSTlJvYpoM6dJw zPyV0Dq1YH98ytv5obcTHTY3ue0Pb6UmYX9iB+OiL5zVKwJb00QeiSj8X+cGGsiv7eo9 MeKxr2sn00T45yKvTKY2VvMMS53Bxb61pgkxFsRUwrSTnIVSstRx4pB1fYpspfnWQ+1V GzG2IKJqbq91v6SatOCMA1RBv3ur1QoLuTF+uoobsRpsBn6qJSk853en54sH1bE1y+48 DoTA== 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.182.121.134 with SMTP id lk6mr17834056obb.51.1435687937207; Tue, 30 Jun 2015 11:12:17 -0700 (PDT) Received: by 10.76.70.199 with HTTP; Tue, 30 Jun 2015 11:12:17 -0700 (PDT) In-Reply-To: References: <20150630162542.34f46f2a@ncopa-desktop.alpinelinux.org> Date: Tue, 30 Jun 2015 11:12:17 -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=089e01536a588172560519c0251a X-Virus-Scanned: ClamAV using ClamSMTP --089e01536a588172560519c0251a Content-Type: text/plain; charset=UTF-8 On second thought, `apk search '*'` spits out a bunch of repeats for some reason. Then there's dev and doc packages. There's only 3364 unique packages. On Tue, Jun 30, 2015 at 10:11 AM, Michael Fox <415fox@gmail.com> wrote: > 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 > -- - Michael --089e01536a588172560519c0251a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On second thought, `apk search '*'` spits out a bu= nch of repeats for some reason. Then there's dev and doc packages. Ther= e's only 3364 unique packages.

=
On Tue, Jun 30, 2015 at 10:11 AM, Michael Fox <4= 15fox@gmail.com> wrote:
Here's all the things I've installed to get= tests to pass:

gnugrep binutils diffutils coreutils linux-headers g= zip 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 rep= ort 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 f= or a month? If so, I volunteer to be one of them.

<= div class=3D"gmail_extra">

On Tue, Jun 30, 2015 at 7:25 AM, Natanael Copa <<= a href=3D"mailto:ncopa@alpinelinux.org" target=3D"_blank">ncopa@alpinelinux= .org> wrote:
On Mon, = 29 Jun 2015 16:53:48 -0700
Michael Fox <415fo= x@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



--

-
Michael
--089e01536a588172560519c0251a-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---