Date: Fri, 20 Jun 2008 19:18:21 +0200 From: Kris Kennaway <kris@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: regression-test Message-ID: <485BE65D.4030909@FreeBSD.org> In-Reply-To: <20080620155310.GA51235@graf.pompo.net> References: <676047.76296.qm@web32706.mail.mud.yahoo.com> <20080619163501.GB12160@atarininja.org> <485A921C.80602@FreeBSD.org> <20080619210519.GV18873@graf.pompo.net> <485B0A6C.3080301@FreeBSD.org> <7d6fde3d0806191854o461d3bddxa44d011e56c4b73b@mail.gmail.com> <20080620155310.GA51235@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Thierry Thomas wrote: > Le Ven 20 jui 08 à 3:54:04 +0200, Garrett Cooper <yanefbsd@gmail.com> > écrivait : > >>>> I try to enable regression-test when possible, but the current >>>> implementation is a post-build target, and some ports' testings need a >>>> post-install target. In these cases, I enclose the regression-test >>>> target between .ifdef MAINTAINER_MODE. >>> I'd say those ports are broken; conceptually, you should be testing whether >>> or not your port works *before* you install it, not after. >>> >>> Kris >> Agreed. Functionality verification is a requirement for acceptance in >> any release structure, not the other way around. > > That's not always so simple: > > - when you run the configure script, it may define some paths (e.g. > DATADIR), and some files under this directory may be required for the > program to be run; > > - some runtime dependencies may be required; > > - the program may be unusable without some additional steps taken into > account by a pkg-install script; Apart from #2 (which I addressed previously), that just means that your regression-test target and/or port patches need to be more complicated to prepare the tests. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485BE65D.4030909>