DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=P26uFPgjBNyoIrdSvaCghwk4cgu1zLTjXFPBgPiX1tVuqy0Hh/QpLKGZLtzHtz0U2E
         +G6hd1JH87tSsD8s5jU+rr5Q262n9p2P/Rkqht/Np7Ba9A5iy4Yy56CnZUwVbeOI+KW+
         UVBLDYKAm/NO8tqPAmydCEGKIM6U/Xf4ABXd8=
Precedence: list
MIME-Version: 1.0
In-Reply-To: <1289383750.18266.23.camel@ncopa-desktop.nor.wtbts.net>
References: <1289383750.18266.23.camel@ncopa-desktop.nor.wtbts.net>
Date: Wed, 17 Nov 2010 22:08:45 -0500
Message-ID: <AANLkTimyzPyuy=_-=zJSHo_VKu60zNSY5qsUhME6jhcY@mail.gmail.com>
Subject: Re: [alpine-devel] Alpine 2.2
From: Jeff Bilyk <jbilyk@gmail.com>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: Alpine Development <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Re: testing and QA, I took a look at APTS (thanks to ncopa pointing it
out...).  Taking the initial idea but simplifying a bit, I figured
taking the following approach might work:

Take the .mk files from svn://svn.alpinelinux.org/apts, strip the
first line and sed apk_delete for apk_del.
Run the following script (a gutted version of run-tests from APTS):
----------
#!/bin/sh -e

# Get file to output to
OUTFILE=3D"$@"
if [ -z "$OUTFILE" ];
 then echo "Usage: $0 outfile" && exit 0;
fi

# Clear file if text
echo "" > $OUTFILE

# Add package, run basic test then remove package
for package in `ls ./packages`;
do sh -e ./packages/$package >> $OUTFILE 2>&1 && echo "$package passed
tests" >> $OUTFILE;
done
----------

A sample of a .mk file that's in SVN that we could adapt: sed.mk:

----------
sed:
	apk_add $@
	echo "hello" | sed 's/hello/world/g' | grep 'world'
	apk_delete $@
	[ `readlink /bin/sed` =3D /bin/busybox ]
----------

The output can be redirected and parsed (or maybe just take stderr?)
so that once edge ISOs are autobuilt, they can have some basic tests
done on most packages (or just the important ones?).  Assuming the ISO
passes this basic QA upload the ISO to the mirrors.  If it fails, add
the output from the script to sircbot's output on alpine-devel so that
the package can be fixed.

Thoughts?

Jeff

On Wed, Nov 10, 2010 at 5:09 AM, Natanael Copa <ncopa@alpinelinux.org> wrot=
e:
> Hi,
>
> So Alpine 2.1 is out and its time to start plan for alpine-2.2. Here are
> some of the things I would like to do for the 2.2 release, scheduled to
> May 2011.
>
> * x86_64 alpine port
> * java support (openjdk)
> * Go Lang support
> * llvm/clang support (maybe we can base alpine-3 completely on clang)
> * improve admin tools, setup-alpine, ACF, unattended installer etc
> * apk-tools: "install_if" (or "conditional groups")
> * lua binding to apk-tools
> * improve abuild (move dependency handling to lua code, build in empty
> chroot)
> * support for cross compiling in abuild?
> * autobuilding of edge snapshot iso images
> * improve testing / quality assurance
> * python3?
> * new version of uclibc, linux kernel, and lots of other new apps
> * Qt support
> * GNOME?
>
> Anything else?
>
> If there are some of the above (or something else) you would like to
> work on, please fell free to let me know. I have various of the above
> stuff partially done already.
>
> If you have some ideas please feel free to send feedback. I'm specially
> interested in ideas what we can do to improve the admin tools,
> setup-alpine, setup-disk and quality assurance.
>
> Thanks!
>
> -nc
>
>
>
> ---
> Unsubscribe: =A0alpine-devel+unsubscribe@lists.alpinelinux.org
> Help: =A0 =A0 =A0 =A0 alpine-devel+help@lists.alpinelinux.org
> ---
>
>



--=20
Jeff


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---