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



On Thu, 2011-11-17 at 12:00 +0200, Noel Grandin wrote:
or (b) your company pays SUSE/Redhat to allocate one of their
developers to it.

        Heh ;-) Of course, there is also Canonical, Lanedo, and any number of
other S/W consulting firms that could help out.

        But - of course you're right; the basic way to get things fixed is to
fix them yourself, and we're eager to help self-motivated problem fixers
with code pointers, tips, build help etc. etc.

        So - indeed, the first step is to get a build. After you have that,
resurrecting the old mdbtools CWS / patch set would be a good idea.

        The -real- reason we havn't shipped mdbtools in anger is that it is not
reliable / good at write support. If we are not writing into the
database - we need to migrate it to something else on load. If we are
migrating it to something else, we want to run hundreds of miles up-hill
rather than migrate tens of thousands of users to using hsqldb in anger.
So we're blocked on getting a nice sqlite backend in-tree that we're
confident enough in to replace hsqldb, such that we can resurrect the
mdbtool stuff so that ... ;-) so it is rather a linked problem.

        OTOH - it'd be great to have help with any part of that you like.

        All the best,

                Michael.

-- 
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


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.