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 <ncopa_at_alpinelinux.org>
> On Mon, 29 Jun 2015 16:53:48 -0700
> Michael Fox <415fox_at_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
> > 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.
Received on Tue Jun 30 2015 - 10:11:59 GMT