interesting
/
getdns
mirror of https://github.com/getdnsapi/getdns.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

release number/date changes

This commit is contained in:
Glen Wiley 2014-05-22 14:16:34 -04:00
parent cd0177451d
commit 350b2025de
2 changed files with 30 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ChangeLog
View File

@ -1,4 +1,4 @@
* 2014-??-??: Version 0.1.2 * 2014-05-22: Version 0.1.2
* Fixed rdata fields for MX * Fixed rdata fields for MX
* Expose only public API symbols * Expose only public API symbols
* Updated manpages * Updated manpages

42
README.md
View File

@ -1,18 +1,24 @@
getdns API getdns API
========== ==========
* Date: 2014-03-24 * Date: 2014-05-22
* GitHub: <https://github.com/getdnsapi/getdns> * GitHub: <https://github.com/getdnsapi/getdns>
getdns is a [modern asynchronous DNS API](http://www.vpnc.org/getdns-api/) intended to make all types of DNS information easily available as described by Paul Hoffman. This implementation is licensed under the New BSD License (BSD-new). getdns is a [modern asynchronous DNS API](http://www.vpnc.org/getdns-api/)
intended to make all types of DNS information easily available as described by
Paul Hoffman. This implementation is licensed under the New BSD License
(BSD-new).
The [getdns-api mailing list](http://www.vpnc.org/mailman/listinfo/getdns-api) is a good place to engage in discussions regarding the design of the API. The [getdns-api mailing list](http://www.vpnc.org/mailman/listinfo/getdns-api)
is a good place to engage in discussions regarding the design of the API.
If you are just getting started with the library take a look at the section below that If you are just getting started with the library take a look at the section
describes building and handling external dependencies for the library. Once it is below that describes building and handling external dependencies for the
built you should take a look at src/examples to see how the library is used. library. Once it is built you should take a look at src/examples to see how
the library is used.
This file captures the goals and direction of the project and the current state of the implementation. This file captures the goals and direction of the project and the current state
of the implementation.
The goals of this implementation of the getdns API are: The goals of this implementation of the getdns API are:
@ -29,22 +35,30 @@ Non-goals (things we will not be doing at least initially) include:
## Language Bindings ## Language Bindings
In parallel, the team is actively developing bindings for various languages. For more information, visit the [wiki](https://github.com/getdnsapi/getdns/wiki/Language-Bindings). In parallel, the team is actively developing bindings for various languages.
For more information, visit the
[wiki](https://github.com/getdnsapi/getdns/wiki/Language-Bindings).
Motivation for providing the API Motivation for providing the API
================================ ================================
The developers are of the opinion that DNSSEC offers a unique global infrastructure for establishing and enhancing cryptographic trust relations. With the development of this API we intend to offer application developers a modern and flexible way that enables end-to-end trust in the DNS architecture and will inspire application developers towards innovative security solutions in their applications. The developers are of the opinion that DNSSEC offers a unique global
infrastructure for establishing and enhancing cryptographic trust relations.
With the development of this API we intend to offer application developers a
modern and flexible way that enables end-to-end trust in the DNS architecture
and will inspire application developers towards innovative security solutions
in their applications.
Releases Releases
======== ========
Release numbering follows the [Semantic Versioning](http://semver.org/) approach. The code is currently under active development. Release numbering follows the [Semantic Versioning](http://semver.org/)
approach. The code is currently under active development.
The following requirements were met as conditions for the present release: The following requirements were met as conditions for the present release:
* code compiles cleanly on at least the primary target platforms: RHEL/CentOS 6.3 Linux, FreeBSD 9.2 * code compiles cleanly on at least the primary target platforms: OSX, RHEL/CentOS Linux, FreeBSD
* examples must compile and be clean * examples must compile and run clean
* clearly document supported/unsupported elements of the API * clearly document supported/unsupported elements of the API
@ -151,7 +165,7 @@ where possible dependencies are identified using the method specific to the plat
We intend to add MS-Windows, Android and other platforms to the releases as we have time to port it. We intend to add MS-Windows, Android and other platforms to the releases as we have time to port it.
##Build Reports ##Platform Specific Build Reports
[![Build Status](https://travis-ci.org/getdnsapi/getdns.png?branch=master)](https://travis-ci.org/getdnsapi/getdns) [![Build Status](https://travis-ci.org/getdnsapi/getdns.png?branch=master)](https://travis-ci.org/getdnsapi/getdns)
@ -159,6 +173,8 @@ We intend to add MS-Windows, Android and other platforms to the releases as we h
If you're using [FreeBSD](http://www.freebsd.org/), you may install getdns via the [ports tree](http://www.freshports.org/dns/getdns/) by running: `cd /usr/ports/dns/getdns && make install clean` If you're using [FreeBSD](http://www.freebsd.org/), you may install getdns via the [ports tree](http://www.freshports.org/dns/getdns/) by running: `cd /usr/ports/dns/getdns && make install clean`
If you are using FreeBSD 10 getdns can be intalled via 'pkg install getdns'.
###CentOS/RHEL 6.5 ###CentOS/RHEL 6.5
We rely on the most excellent package manager fpm to build the linux packages which We rely on the most excellent package manager fpm to build the linux packages which