summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20130104/9b041514
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/attachments/20130104/9b041514
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20130104/9b041514')
-rw-r--r--zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment-0001.html4
-rw-r--r--zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment.html4
2 files changed, 8 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment-0001.html
new file mode 100644
index 000000000..7ef08e5a7
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment-0001.html
@@ -0,0 +1,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>
diff --git a/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment.html b/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment.html
new file mode 100644
index 000000000..7ef08e5a7
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130104/9b041514/attachment.html
@@ -0,0 +1,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>