summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment.html
blob: 7ef08e5a7fdd08905e6a1c3cf4e6e771cf7900b8 (plain)
1
2
3
4
<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/1/4 Guillaume Rousse <span dir="ltr">&lt;<a href="mailto:guillomovitch@gmail.com" target="_blank">guillomovitch@gmail.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We already run existing tests suite during package build... Running them again on a different host would just change the execution environment to use runtime dependencies instead of build time dependencies. I don&#39;t know if the potential results are worth the additional infrastructure needed.</blockquote>
</div><br></div><div class="gmail_extra" style>I was under the impression, that only some kind of lint checking of the RPM was performed. I&#39;m talking about checking the functionality of the packaged software. Are you already doing that? What kind of tests are performed during packaging?</div>
</div>