On Thu, Apr 26, 2012 at 10:23:00AM +0200, Vít Ondruch wrote:
Hi Ken,
On specs, tests, etc, we apply documentation packaging guidelines
[1] and this is quote from reviewers guide:
*MUST*: If a package includes something as %doc, it must not affect
the runtime of the application. To summarize: If it is in %doc, the
program must run properly if it is not present.
I interpret is in this way: specs, tests, etc are not essential for
package runtime, therefore I place them in -doc subpackage. Typical
user is not installing -doc subpackage, so he does not waste his
disk space. Also, test suite may help in better understanding how
the library works, therefore it might be view as as documentation.
So if there is test suite, keep it, if there is non, do nod add it.
Its question to upstream if you have different opinion.
The inclusion of test suite in gem is more generic question for Ruby
community. For example Rails does not include its test suite and I
find it correct. On the other hand, there is some infrastructure in
RubyGems which should allow to execute the test suite of gem during
installation, but I never tried it personally, I don't believe it
will work reasonably.
I think this is very logical. The test suite is more for development use
and not for runtime. At best I would include them in a -devel package,
but would side on not packaging them at all since they're more volatile.
Their benefit, WRT packaging, is in executing them during the package's
build to ensure the code being packaged works as expected.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/