From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 1/3] New package: berkeley db 6.1.26
Date: Thu, 18 Feb 2016 17:24:42 +0100 [thread overview]
Message-ID: <ABFD811D-69E6-4E38-9AAC-54A6A1A514AE@ipfire.org> (raw)
In-Reply-To: <1455736216.12368.1.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2946 bytes --]
Hi all,
have tried to build the newer version of BerkeleyDB only and without a DB4 compat a while ago and a complete buildthrough needed patches for OpenLDAP, PHP (have patched it for DB6 in the updated version PHP-5.6.17 will deliver it in the next days) and squidGuard but i haven´t collected good testing results with this basics at this time but you can find in here --> http://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=749c518093e887f614a91d73fdefcb64f14aa952 the needed patches for a DB6 only environment.
Nevertheless a lot of software still uses BDB in version 5 or 4. Like PHP, the sources need´s then to be patched to be compatible with a BerkeleyDB-6 only installation, so a compat version 4 might be a good idea in my opinion.
Greetings,
Erik
Am 17.02.2016 um 20:10 schrieb Michael Tremer <michael.tremer(a)ipfire.org>:
> On Wed, 2016-02-17 at 07:58 +0100, Marcel Lorenz wrote:
>> Hi,
>>
>> sorry, i use Outlook to read this mails. First i not see all your
>> comments in your answer.
>> I move this mail to my roundcube test system and i found the
>> comments. :-)
>>
>> The db6 package cannont replace the db4. Some componsts will fails
>> build with
>> only the new db6 header files. I try the hard way to patch this
>> packages and i giving up. To many and endless problems.
>>
>> This package is primary for the later postfix 3 integration.
>> Some other packages will found automatically the db6 header in the
>> db6 subfolder. (Apache 2.4, Postfix 3 i seen)
>>
>> I will make a new and better patch. This was my first try for the
>> maillinglist... ;-)
>>
>> Ps. Please tell me when i write nonsense in english...
>
> You don't.
>
> Please include this information (that it won't replace db4, and that
> this is for postfix) in the patch, too.
>
> Best,
> -Michael
>
>>
>> Marcel
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Development [mailto:development-bounces(a)lists.ipfire.org] Im
>> Auftrag von Michael Tremer
>> Gesendet: Dienstag, 16. Februar 2016 19:03
>> An: Marcel Lorenz <m.lorenz(a)ml-systec.de>
>> Cc: development(a)lists.ipfire.org
>> Betreff: Re: AW: [PATCH 1/3] New package: berkeley db 6.1.26
>>
>> Hi,
>>
>> that these were sent in one patchset is not an issue (as I said). The
>> other things that I commented inline though are. Are you going to do
>> anything about them?
>>
>> I think there is no point to look at any new patches that include the
>> same mistakes.
>>
>> -Michael
>>
>> On Thu, 2016-02-11 at 06:28 +0000, Marcel Lorenz wrote:
>>> Hi,
>>>
>>> this are all single patches. I had problems to send patches
>>> to the
>>> list.
>>> I use the "git send-email --annotate -3" command for my last 3
>>> changes.
>>> This was new for me, that there are "connectet"
>>>
>>> The first with db6 are not in the pach list. How i can correct
>>> this?
>>>
>>> Marcel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
prev parent reply other threads:[~2016-02-18 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b19758ecdfd463bbdc65bd7fb85cef8@srv01.kits.local>
2016-02-16 18:03 ` AW: " Michael Tremer
2016-02-17 6:58 ` AW: " Marcel Lorenz
2016-02-17 19:10 ` Michael Tremer
2016-02-18 16:24 ` ummeegge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ABFD811D-69E6-4E38-9AAC-54A6A1A514AE@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox