Lucas Nussbaum escreveu isso aí: > On 20/08/11 at 12:50 -0700, Antonio Terceiro wrote: > > Lucas Nussbaum escreveu isso aí: > > > Package: gem2deb > > > Version: 0.2.6 > > > Severity: wishlist > > > > > > Hi, > > > > > > It would be great if gem2deb made it easier to create packages that can > > > be tested by autopkgtest. See http://dep.debian.net/deps/dep8/ > > > > > > I don't have any specific idea about that, but it's something that we > > > should monitor, and for which we could be early adopters. > > > > We could automatically generate a debian/tests/control in a way that > > gem2deb's test_runner is called with an argument that makes it run the > > automated tests in the packages without any $LOAD_PATH manipulation, so > > that the tests would run against the installed code. > > I'm wondering whether we should copy the tests to a temporary place, to > avoid LOAD_PATH manipulations with idioms such as: > $:.unshift '../lib'
Supposedly the package maintainer should take care of that by patching the test suite accordingly to make sure the tests are run against the code installed in the package build directory and not the code in the source package. But I think you could try doing that anyway. The problem is that we only known exactly which are *the tests* to be copied when the test files are explicitly listed by upstream in the gemspec or by us in debian/ruby-tests.yaml. Maybe we could copy everything except lib/ and any directory containing binary extensions. I can imagine a lot of corner cases, though. -- Antonio Terceiro <terce...@debian.org>
signature.asc
Description: Digital signature
