Date: prev next · Thread: first prev next last


On Mon, 2011-01-31 at 09:31 -0700, Jeff Chimene wrote:
On 01/31/2011 09:20 AM, drew wrote:
On Mon, 2011-01-31 at 11:14 -0500, drew wrote:
On Mon, 2011-01-31 at 09:03 -0700, Jeff Chimene wrote:
On 01/31/2011 08:00 AM, drew wrote:
Hi,

First in a couple emails today regarding the TDF/LibreOffice booth at
SCALE.

HI Drew:

Thanks for this effort.

What are your thoughts about also including ODBC and JDBC drivers?

Easy answer - license (you know which ones :) and links please - I can
see no reason to waist perfectly good tracks on a blank DVD.

sqlite w/ jdbc driver would be nice IMO.


sorry for the double post.

I was thinking about a windows version of MySQL, but I'm really not sure
on that. Thoughts?

Yes. There's an interesting implementation of a LAMP stack: XAMPP

http://www.apachefriends.org/en/xampp-windows.html

Very nice. Performs well on my Windows 7/64 laptop. I think it's best w/
Cygwin, but I haven't used it w/o Cygwin.


Well my only reservation as I think about this in general is that this
is a one off disc for a Linux festival and maybe hitting the windows
stuff too strong is not the way to go - are you thinking of having the
complete xampp distro on the disc?


-- 
Unsubscribe instructions: E-mail to marketing+help@us.libreoffice.org
List archive: http://listarchives.libreoffice.org/us/marketing/
*** All posts to this list are publicly archived for eternity ***

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.