Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 526
    • Issues 526
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #88

Closed
Open
Created Feb 21, 2018 by Ondřej Surý@ondrejOwner

Make all BIND libraries private

BIND currently exports number of libraries, but there's virtually no external projects that we are aware of that would be using those libraries. Keeping the ABI and API stable is big burden, and we are exploring possibility of merging all the libraries into a tightly-coupled private library that wouldn't be used outside of BIND (and tools) effectively making those libraries private.

The BIND 9.13/9.14 would be the first release that would drop the libraries.

The BIND 9.11 ESV would keep those libraries until 2022, so any external users would have enough time to migrate to other DNS libraries.

Known external users of libisc and friends:

  • ISC DHCP (will continue using BIND 9.11 libraries)
  • dnsperf (either use BIND 9.11 libraries, or make it ISC project)
Assignee
Assign to
Time tracking