From ooo-dev-return-10117-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Mon Dec 5 14:25:32 2011 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E62917395 for ; Mon, 5 Dec 2011 14:25:31 +0000 (UTC) Received: (qmail 46012 invoked by uid 500); 5 Dec 2011 14:25:31 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 45966 invoked by uid 500); 5 Dec 2011 14:25:31 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 45958 invoked by uid 99); 5 Dec 2011 14:25:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2011 14:25:31 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of orwittmann@googlemail.com designates 209.85.161.47 as permitted sender) Received: from [209.85.161.47] (HELO mail-fx0-f47.google.com) (209.85.161.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Dec 2011 14:25:24 +0000 Received: by faas12 with SMTP id s12so601003faa.6 for ; Mon, 05 Dec 2011 06:25:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0pzReZsEkaBZQgg4TwYMTERTPO7EtVMQfL8ierSa6XY=; b=b1JjfZBP6nHAgeL40gExc/u8LUslmzwIbDpLwGyZSR627EAlYm/SscDIqFlIE0WNNo 7jTpffrnHOw0xAzpfK5pgcz0RYVWXSrM6MuG+az/7b7SxwqoQwoU3Aahp/ebgXbHHilW a9dms6UsrTm81c2+L0A5UauKMux47j9HA60Jk= Received: by 10.180.105.232 with SMTP id gp8mr13009868wib.65.1323095103994; Mon, 05 Dec 2011 06:25:03 -0800 (PST) Received: from [9.155.131.24] (deibp9eh1--blueice3n2.emea.ibm.com. [195.212.29.180]) by mx.google.com with ESMTPS id 4sm7583644wbx.11.2011.12.05.06.24.58 (version=SSLv3 cipher=OTHER); Mon, 05 Dec 2011 06:24:59 -0800 (PST) Message-ID: <4EDCD442.2060405@googlemail.com> Date: Mon, 05 Dec 2011 15:25:06 +0100 From: Oliver-Rainer Wittmann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [code] usage of Berkeley DB References: <4EDCB9D0.90209@googlemail.com> In-Reply-To: <4EDCB9D0.90209@googlemail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 05.12.2011 13:32, Oliver-Rainer Wittmann wrote: > Hi, > > here is the status of my findings regarding the usage of the Berkeley DB: > > It is used in modules l10ntools, xmlhelp and desktop. > > In module l10ntools it is used by 'dead code' in a tool called 'HelpLinker'. The > 'HelpLinker' tool is used in module helpcontent2 to prepare the help content > data for the help system. As this is 'dead code' I have already removed it in my > local environment. I have checked the resulting installation and the help system > still works. > > In module xmlhelp it is used for the help system to _read_ Berkeley DB files. As > far as I have figured out the Berkeley DB files which may be accessed are the > ones which may have been created by the preparing the help content data. > As such Berkeley DB files are no longer created - see above - I am currently > removing the code accessing Berkeley DB files in module xmlhelp in my local > environment. I will follow-up on this here, when I have checked the resulting > installation. I have checked the resulting installation of my local environment having removed the Berkeley DB usage code from xmlhelp. The help system works - at least my test cases. Also, the help content of a new installed extension is working in the help system. > > In module desktop it is used for the management of installed extensions. For > each installed extension a key-value-pair is stored in a Berkeley DB file. There > are created certain Berkeley DB files in an installation for various purposes. > The intrinsic data type of the 'key' and the 'value' is . > > Thus, it looks like that we only have one 'real' dependence on Berkeley DB - the > management of extensions. > > feedback/comments/support is welcome. > > Best regards, Oliver.