summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20121120/21bd8bd4')
-rw-r--r--zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment-0001.html17
-rw-r--r--zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment.html17
2 files changed, 34 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment-0001.html
new file mode 100644
index 000000000..ce4e5575a
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment-0001.html
@@ -0,0 +1,17 @@
+<br><br><div class="gmail_quote">On Tue, Nov 20, 2012 at 11:20 PM, Juan Luis Baptiste <span dir="ltr">&lt;<a href="mailto:juancho@mageia.org" target="_blank">juancho@mageia.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+<br><br><div class="gmail_quote"><div class="im">On Tue, Nov 20, 2012 at 12:54 AM, andre999 <span dir="ltr">&lt;<a href="mailto:andre999mga@laposte.net" target="_blank">andre999mga@laposte.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+
+An alternate approach would be to package and distribute the documentation separately (as nonfree).  Oracle permits this as long as it is only available on the same media or sites as mysql-workbench -- which concurs with our current practices.<br>
+
+
+
+Then the mysql-workbench package itself would still be GPL.<br>
+<br>
+So I&#39;d go for the second option.<br>
+Maybe adding a comment in the mysql-workbench description indicating that due to licensing restrictions, the documentation is available in non-free.<br><br></blockquote><div> </div></div></div></blockquote><div><br></div>
+
+<div>Giving it a second thought, I think this isn&#39;t a good idea because if I split the documentation into a separate package that would mean that I would need to have mysql-workbench sources also in the documentation package to be able to build it. And looking more closely at the Fedora patch, they remove the documentation but patch the program to open the online version of the documentation. IMO, if we can&#39;t include the doc in the same mysql-workbench package then the online approach is better. </div>
+
+<div> </div></div>-- <br>Juancho<br>
diff --git a/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment.html b/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment.html
new file mode 100644
index 000000000..ce4e5575a
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20121120/21bd8bd4/attachment.html
@@ -0,0 +1,17 @@
+<br><br><div class="gmail_quote">On Tue, Nov 20, 2012 at 11:20 PM, Juan Luis Baptiste <span dir="ltr">&lt;<a href="mailto:juancho@mageia.org" target="_blank">juancho@mageia.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+<br><br><div class="gmail_quote"><div class="im">On Tue, Nov 20, 2012 at 12:54 AM, andre999 <span dir="ltr">&lt;<a href="mailto:andre999mga@laposte.net" target="_blank">andre999mga@laposte.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+
+
+An alternate approach would be to package and distribute the documentation separately (as nonfree).  Oracle permits this as long as it is only available on the same media or sites as mysql-workbench -- which concurs with our current practices.<br>
+
+
+
+Then the mysql-workbench package itself would still be GPL.<br>
+<br>
+So I&#39;d go for the second option.<br>
+Maybe adding a comment in the mysql-workbench description indicating that due to licensing restrictions, the documentation is available in non-free.<br><br></blockquote><div> </div></div></div></blockquote><div><br></div>
+
+<div>Giving it a second thought, I think this isn&#39;t a good idea because if I split the documentation into a separate package that would mean that I would need to have mysql-workbench sources also in the documentation package to be able to build it. And looking more closely at the Fedora patch, they remove the documentation but patch the program to open the online version of the documentation. IMO, if we can&#39;t include the doc in the same mysql-workbench package then the online approach is better. </div>
+
+<div> </div></div>-- <br>Juancho<br>