https://bugzilla.redhat.com/show_bug.cgi?id=1173773
--- Comment #3 from Remi Collet <fed...@famillecollet.com> --- (In reply to Adam Williamson (Fedora) from comment #1) > The 'autoloader' for purpose of running the unit tests is of course > ridiculous and would break the moment upstream touches pretty much anything. I use a lot the "phpab" command which allow to create a very simple autoloader. For example, for this library: $ phpab --output bootstrap.php --exclude *Test.php --basedir . src tests phpab 1.16.2 - Copyright (C) 2009 - 2014 by Arne Blankerts Scanning directory src Scanning directory tests Autoload file bootstrap.php generated. $ phpunit --bootstrap bootstrap.php PHPUnit 4.4.0 by Sebastian Bergmann. Configuration read from /tmp/php-bantu-ini-get-wrapper-1.0.1-1.fc22.src/php-ini-get-wrapper-1.0.1/phpunit.xml.dist ............................................................ Time: 55 ms, Memory: 4.75Mb OK (60 tests, 60 assertions) In some case, it could even make sense to provide a generated autoload.php, which could make it simpler for consumers of the library (see all the PHPUnit stack for example). $ phpab --output src/autoload.php src At least, this autoloader is correct (not like the tricky composer one, which is not even not PSR-0 compliant...) -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review
