Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hi,

I've tried creating an extension entry on the new extensions site, but :

1) I see no way to currently upload the extension ;
2) Perhaps (1) is dependent on the extension project being authorised ?
3) Where does one stipulate the licence conditions, or do they all come
under a one-hat fits all licence ?


The reason I'm asking is that I've built the MySQL Native C Connector
extension against master, and it works both on a master build and the
current production builds for LibreOffice, but my understanding of the
MySQL libmysql library is that it would have to be released as GPL (as
indeed it was on the Sun/Oracle extension site). If the site does not
cater for that I will withdraw my request for approval of the project.

Bear in mind that I'm not in a position to currently provide connectors
for Windows or Linux (although I could set up a build box for Linux in
the long run, but its a real pain to have to build everything just to
get a single extension out of it).


Alex


-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.