From Fedora Project Wiki

< Changes

Revision as of 12:52, 8 April 2014 by Jstanek (talk | contribs) (Created page with "<!-- Self Contained or System Wide Change Proposal? Use this guide to determine to which category your proposed change belongs to. Self Contained Changes are: * changes to is...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


BerkeleyDB 6

Summary

Add BerkeleyDB v. 6, which changed license from previous releases (GPLv2 to AGPLv3), to Fedora while keeping the older version for packages which cannot use BerkeleyDB with the new license.

Owner

  • Name: Jan Staněk
  • Email: <jstanek@redhat.com>
  • Release notes owner:

Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-04-08
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The BerkeleyDB, used between others by Package-x-generic-16.pngrpm, changed license between versions 5.* and 6.* to AGPLv3 from GPLv2. As those two licenses are not compatible, packages using the BerkeleyDB either has to change its license to AGPLv3 compatible, keep on using the older BerkeleyDB or use another DB entirely.

Target of this change is to create new set of packages from current Package-x-generic-16.pnglibdb, which contains the v5 version, and keep it alongside the latest BerkeleyDB.

Benefit to Fedora

This change enables projects and packages to use BerkeleyDB with GPLv2 license, allowing them to work until the upstream makes their decision about the license change, and at the same time do not restricts projects which already adopted the BerkeleyDB with new license to the older versions of it.

Scope

  • Proposal owners: Create new set of packages and introduce proper versioning in order to not confuse the dynamic linker.
  • Other developers: Packages dependent on libdb would have to specify which version they want to use (specify version in the spec Requires: field). Rebuilds of dependent packages will be necessary.
  • Release engineering: None
  • Policies and guidelines: None

Upgrade/compatibility impact

If the versioning of the symbols will be implemented in the v5, user-built software linked against it will need to be rebuilt.

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? N/A (not a System Wide Change), Yes/No
  • Blocks product? product

Documentation

N/A (not a System Wide Change)

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/BerkeleyDB_6&oldid=375711"