FS#39907 - [redland] "./configure --with-bdb=no" breaks applications

Attached to Project: Arch Linux
Opened by Jiri Prochazka (ojirio) - Wednesday, 16 April 2014, 18:25 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 16 April 2014, 19:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tom Gundersen (tomegun)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The package is configured with ./configure --with-bdb=no which excludes the bdb store which is required by some applications.
There are separated packages for other storages, but not the bdb in-memory store, so there is no way to get it at the moment.

Additional info:
* package version: 1:1.0.17-2
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 16 April 2014, 19:25 GMT
Reason for closing:  Won't fix
Comment by Dave Reisner (falconindy) - Wednesday, 16 April 2014, 18:35 GMT
What are these "some applications" which require a specific backend? Berkeley DB support was intentionally dropped because of the restrictive licensing.
Comment by Jiri Prochazka (ojirio) - Wednesday, 16 April 2014, 18:57 GMT
For example my application which isn't available in repositories nor AUR. When I updated the redland package, it started silently failing.
Comment by Jiri Prochazka (ojirio) - Wednesday, 16 April 2014, 19:05 GMT
I've been told these licensing concerns are being raised as a response to Oracle licensing changes of BDB 6. Maybe there could be a db5 package made as a dependency for packages like this?
Comment by Dave Reisner (falconindy) - Wednesday, 16 April 2014, 19:07 GMT
I think you'll need to either fix your own application or compile your own redland. Seems really weird that you're depending on an implementation detail of the storage backend when it should just be abstracted away.

Loading...