From: Jeff Garzik <jeff@garzik.org>
To: Samba - BoYang <boyang@samba.org>
Cc: hail-devel@vger.kernel.org
Subject: Re: CLD doesn't build on db-4.3
Date: Thu, 01 Apr 2010 11:03:48 -0400 [thread overview]
Message-ID: <4BB4B5D4.2000300@garzik.org> (raw)
In-Reply-To: <4BB47D27.6080405@samba.org>
On 04/01/2010 07:01 AM, Samba - BoYang wrote:
> hi, *
> CLD doesn't build on db-4.3 on suse 11, since db-4.3 uses deprecated
> structure members DBC->c_xxx(c_close(), etc) instead of DBC->xxx. :-)
>
> It won't build on db-4.4, either. probably won't build on db-4.5, as
> db-5.0 says DBC->xxx was introduced in db-4.6. :-) Should we disable
> support for 4.3 - 4.5 and add 4.9 - 5.0?
I'd answer "yes", by a circuitous route: if I understand things
correctly, the replicated PAXOS db4 backend that we are heading towards
(see the 'replica' branch of
git://git.kernel.org/pub/scm/daemon/cld/cld.git) was buggy in early db4
releases.
Therefore, it sounds like we could eliminate two issues with a single
change, by removing support for db 4.3 - 4.5, the DBC issue and the
PAXOS issue.
I'm fine with adding support for 4.9+ as long as the APIs function in a
compatible manner.
Want to create the simple patch for this? :)
Thanks,
Jeff
next prev parent reply other threads:[~2010-04-01 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 11:01 CLD doesn't build on db-4.3 Samba - BoYang
2010-04-01 13:56 ` Pete Zaitcev
2010-04-01 15:03 ` Jeff Garzik [this message]
2010-04-01 20:50 ` Pete Zaitcev
2010-04-02 0:38 ` Samba - BoYang
2010-04-02 0:35 ` Samba - BoYang
2010-04-14 4:32 ` Jeff Garzik
2010-04-14 4:59 ` Pete Zaitcev
2010-04-14 10:44 ` Here is small patch to enable link against higher-version db for nfs4d and tabled. :-) Samba - BoYang
2010-04-14 13:40 ` Jeff Garzik
2010-04-14 13:50 ` Samba - BoYang
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=4BB4B5D4.2000300@garzik.org \
--to=jeff@garzik.org \
--cc=boyang@samba.org \
--cc=hail-devel@vger.kernel.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