Hi! After reading this bug report, I started thinking of better ways to solve this problem. Then I continued reading debian-devel@l.d.o and found out [0], wich is, I think, a very similar problem.
I think that the proposals in [1] are indeed better solutions than tagging this as wontfix: 1) run the tests during build and include the results 2) include the test suite to be run on the users system 3) provide a little script to run the test suite and to compare the results with the results generated by the buildd. Taking either (1) or (2) would be fine, (1) and (2) sounds very fine and the three of them excellent (although maybe too much work). With this, libeigen2-dev can be switched back to arch-independent, become nicer with multiarch (at least I expect that) and test suites being provided. [0] <http://lists.debian.org/debian-devel/2012/01/msg00130.html> [1] <http://lists.debian.org/debian-devel/2012/01/msg00511.html> Kinds regards, Lisandro. -- I am two fools, I know, for loving, and for saying so. John Donne Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
signature.asc
Description: This is a digitally signed message part.
