Featured Articles

AMD Never Settle Forever bundle hits 200-series cards

AMD Never Settle Forever bundle hits 200-series cards

AMD’s Never Settle bundles have been around for a while and the community response has been extremely positive. When AMD launched…

More...
AMD shipping Beema APUs

AMD shipping Beema APUs

According to Lisa Su, SVP & GM, Global Business Units at AMD, Beema notebook parts have started shipping to manufacturers last…

More...
IHS teardown reveals Galaxy S5 BOM

IHS teardown reveals Galaxy S5 BOM

Research firm IHS got hold of Samsung’s new flagship smartphone and took it apart to the last bolt to figure out…

More...
Galaxy S5, HTC One M8 available selling well

Galaxy S5, HTC One M8 available selling well

Samsung’s Galaxy S5 has finally gone on sale and it can be yours for €699, which is quite a lot of…

More...
KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 GTX 780 Ti Hall Of Fame reviewed

KFA2 gained a lot of overclocking experience with the GTX 780 Hall of Fame (HOF), which we had a chance to…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Monday, 08 July 2013 09:57

Oracle changes license of Berkeley Database

Written by Nick Farell

oracle

Significant change for Web developers

Oracle has changed the license of its embedded database library, Berkeley DB. The software is widely used as a key-value store within other applications and historically used an OSI-approved strong copyleft license which was similar to the GPL.

Under that license, distributing software that embedded Berkeley DB involved also providing "information on how to obtain complete source code for the DB software and any accompanying software that uses the DB software."

Now future versions of Berkeley DB use the GNU Affero General Public License (AGPL). This says "your modified version must prominently offer all users interacting with it remotely through a computer network ... an opportunity to receive the Corresponding Source of your version."

This will cause some problems for Web developers using Berkeley DB for local storage. Compliance has not really been an issue because they never "redistributed" the source of their Web apps.Now they will have to make sure their whole Web app is compliant with the AGPL and make full corresponding source to their Web application available.

They also need to ensure the full app has compatible licensing. Practically that means that the whole source code has to be licensed under the GPLv3 or the AGPL.

Nick Farell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

To be able to post comments please log-in with Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments