From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-November/020166.html | 127 +++++++++++++++++++++++++++ 1 file changed, 127 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-November/020166.html (limited to 'zarb-ml/mageia-dev/2012-November/020166.html') diff --git a/zarb-ml/mageia-dev/2012-November/020166.html b/zarb-ml/mageia-dev/2012-November/020166.html new file mode 100644 index 000000000..592b6e293 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-November/020166.html @@ -0,0 +1,127 @@ + + + + [Mageia-dev] Question about mysql-workbench documentation license + + + + + + + + + +

[Mageia-dev] Question about mysql-workbench documentation license

+ andre999 + andre999mga at laposte.net +
+ Thu Nov 22 12:51:30 CET 2012 +

+
+ +
Juan Luis Baptiste a écrit :
+>
+>
+> On Tue, Nov 20, 2012 at 11:20 PM, Juan Luis Baptiste <juancho at mageia.org
+> <mailto:juancho at mageia.org>> wrote:
+>
+>
+>
+>     On Tue, Nov 20, 2012 at 12:54 AM, andre999 <andre999mga at laposte.net
+>     <mailto:andre999mga at laposte.net>> wrote:
+>
+>         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.
+>         Then the mysql-workbench package itself would still be GPL.
+>
+>         So I'd go for the second option.
+>         Maybe adding a comment in the mysql-workbench description
+>         indicating that due to licensing restrictions, the documentation
+>         is available in non-free.
+>
+>
+> Giving it a second thought, I think this isn'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't include the doc in
+> the same mysql-workbench package then the online approach is better.
+> --
+> Juancho
+
+Online would work, but personally I don't like online documentation, as 
+it ends up being downloaded every time it is referred to.
+
+I like your idea of giving a suggest if the documentation is in a 
+separate package.
+As for as packaging the documentation, you could always download it 
+directly from Oracle if that is easier.
+
+I don't see why you would need mysql-workbench sources in the 
+documentation package.
+Oracle only requires that the documentation, to be redistributed, is 
+presented on an iso or web site where mysql-workbench is *also* 
+available.  (Whether or not in the same package.)
+
+Our mirror policy says that an official mirror must carry core and 
+nonfree.  (We have no control over or responibility for non-official 
+mirrors.)
+And our isos don't have nonfree documentation.  (But if they did, we 
+could always ensure that the documentation package would only be 
+included if the software package were also included.)
+
+So where-ever we put the documentation package (in nonfree), there will 
+also be the mysql-workbench package (in core), which satisfies Oracles 
+restrictions.
+
+Regards :)
+
+-- 
+André
+
+ + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1