I package a few Python modules and enable build-time testing in them for
at least some QA. Some of the packages, although being pure Python
(thus architecture all), deal with data I/O thus prone to bugs related
to alignment/endianness etc. Unfortunately I cannot spot those until
some dependent on them package hits them (e.g. happened quite a few
times with nibabel - nipy bundle). Ideally I wish I could somehow
instruct build servers to build those source packages with only arch:all
binary packages, discarding any result and only keeping the logs.
I wonder if that is somehow possible to achieve cleanly ?
weak alternative could be to enable testing of such core package within
another dependent arch:any package debian/rules (e.g. test nibabel
within nipy's debian/rules) but that is ugly for various reasons.
So I thought to ask ;-)
Cheers,
--
Yaroslav O. Halchenko
Postdoctoral Fellow, Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120621172100.GD5788@onerussian.com">http://lists.debian.org/20120621172100.GD5788@onerussian.com