DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=vGOpVfcRndZ0cLhk7stFGhe9opRB+wEOd6pqu1mvLDgmEvAG9jKRGxhVZFphXuSzSR
         tQSb3Ch3FkVFDu5L+Usjlc3WJEbnMPP9EGHcbyr5mH95CaDIN//za4CEydQHPJPyWCbN
         9P8F4BsdqWRoHaCz2HzKrVoPM4RfIzS3yg9tU=
Precedence: list
MIME-Version: 1.0
Date: Mon, 13 Dec 2010 22:05:01 -0500
Message-ID: <AANLkTin516LifzGKCQ-UR=_tvmbdqudnVNR7YHKChrj7@mail.gmail.com>
Subject: [alpine-devel] Alpine package testing
From: Jeff Bilyk <jbilyk@gmail.com>
To: Alpine Development <alpine-devel@lists.alpinelinux.org>
Content-Type: text/plain; charset=ISO-8859-1

Hello All,

I've been working on getting automatic package testing working using a
new version of APTS (Alpine Package Testing Suite).  Currently it
relies on a file, which is basically a set of shell commands to test a
package.  However, this means that for each package a file needs to be
created.  I'd like to simply this by adding a function to APTS which
will test any daemon automatically (daemon would be detected by
existence of an init.d script) by running it's init script, waiting a
second or two, then stopping the script.  The only thing preventing me
from implementing this is the fact that at least one package (samba)
and possibly more ship without a default config that allows the daemon
to start.  Would it be worth setting some sort of standard for
packages which would require a working default config?

-- 
Jeff


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---