Hi,
On Mon, Jun 13, 2011 at 11:40:35AM +0100, Michael Meeks wrote:
On Mon, 2011-06-13 at 12:21 +0200, Petr Mladek wrote:
Hmm, the patch just disables installation. I am not that happy with such
partial solution. It leaves mess in the sources. I would prefer to
either make the build/installation optional or remove the code at all.
Well - lets disable it by default for now; and drop it for 4.0 if
no-one has turned up to care about and fix it. It can always be
built/shipped as an extension I guess.
I didn't want to remove it completely (at least for now); someone told me
the code could still be useful as an educational tool.
There may also be some users who will not be aware of the change until
the next version of LO is released.
IMHO, about the code removal should decide LO steering committee.
Michael?
Sounds good - I've pushed it on the agenda, perhaps Francois can turn
up and share his analysis - perhaps he can persuade us to kill the code
completely :-) [ or persuade Software AG to invest to maintain and
improve it: who knows ].
I doubt Software AG is interested; the freeware version of Adabas D has a big
version gap with the latest release. IMHO the code is abandonware and they
only provide it by habit / because they had a special deal with Stardivision
and/or Sun in the past.
I asked about the status of Adabas D on discuss@ and various IRC channels;
most of my findings are in this thread:
http://listarchives.documentfoundation.org/www/discuss/msg06607.html
--
Francois Tigeot
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.