The back-ndb backend has never been finished, and relies on partnership with a corporation that has no desire to continue the work since it acquired the original entity involved.
I would suggest then that it be removed from the 2.5 release tree and left master only.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
I'd go further and propose simply deleting back-ndb. Do we know of anyone using it?
--On Monday, March 23, 2020 6:03 PM -0700 Ryan Tandy ryan@nardis.ca wrote:
I'd go further and propose simply deleting back-ndb. Do we know of anyone using it?
It's not usable, so no. ;) There's one ITS around it from someone who made the mistake of attempting to use it.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Ryan Tandy wrote:
I'd go further and propose simply deleting back-ndb. Do we know of anyone using it?
Unlikely, unless for very very simple use cases.
On reconsideration, I don't like the churn that "master-only" causes in our autoconf/makefile stuff. Just leave it in the release and default it to disabled.
--On Tuesday, March 24, 2020 7:45 PM +0000 Howard Chu hyc@symas.com wrote:
Ryan Tandy wrote:
I'd go further and propose simply deleting back-ndb. Do we know of anyone using it?
Unlikely, unless for very very simple use cases.
On reconsideration, I don't like the churn that "master-only" causes in our autoconf/makefile stuff. Just leave it in the release and default it to disabled.
It already defaults to disabled, but it gets picked up when people do things like --enable-backends=mod.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
--On Tuesday, March 24, 2020 12:55 PM -0700 Quanah Gibson-Mount quanah@symas.com wrote:
On reconsideration, I don't like the churn that "master-only" causes in our autoconf/makefile stuff. Just leave it in the release and default it to disabled.
It already defaults to disabled, but it gets picked up when people do things like --enable-backends=mod.
How about we remove it from the list of backends in configure.in (thus --enable-backends won't pick it up). Thus someone would have to explicitly do --enable-ndb=XXX to enable it.
--Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
Quanah Gibson-Mount wrote:
The back-ndb backend has never been finished, and relies on partnership with a corporation that has no desire to continue the work since it acquired the original entity involved.
I would suggest then that it be removed from the 2.5 release tree and left master only.
Sounds fine.
-
Howard Chu -
Quanah Gibson-Mount -
Ryan Tandy