|author||Robin H. Johnson <email@example.com>||2015-08-08 13:49:04 -0700|
|committer||Robin H. Johnson <firstname.lastname@example.org>||2015-08-08 17:38:18 -0700|
proj/gentoo: Initial commit
This commit represents a new era for Gentoo: Storing the gentoo-x86 tree in Git, as converted from CVS. This commit is the start of the NEW history. Any historical data is intended to be grafted onto this point. Creation process: 1. Take final CVS checkout snapshot 2. Remove ALL ChangeLog* files 3. Transform all Manifests to thin 4. Remove empty Manifests 5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$ 5.1. Do not touch files with -kb/-ko keyword flags. Signed-off-by: Robin H. Johnson <email@example.com> X-Thanks: Alec Warner <firstname.lastname@example.org> - did the GSoC 2006 migration tests X-Thanks: Robin H. Johnson <email@example.com> - infra guy, herding this project X-Thanks: Nguyen Thai Ngoc Duy <firstname.lastname@example.org> - Former Gentoo developer, wrote Git features for the migration X-Thanks: Brian Harring <email@example.com> - wrote much python to improve cvs2svn X-Thanks: Rich Freeman <firstname.lastname@example.org> - validation scripts X-Thanks: Patrick Lauer <email@example.com> - Gentoo dev, running new 2014 work in migration X-Thanks: Michał Górny <firstname.lastname@example.org> - scripts, QA, nagging X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed
Diffstat (limited to 'net-dns/fpdns/metadata.xml')
1 files changed, 31 insertions, 0 deletions
diff --git a/net-dns/fpdns/metadata.xml b/net-dns/fpdns/metadata.xml
new file mode 100644
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+A nameserver basically responds to a query. Interoperability is an obvious
+requirement here. The standard protocol behaviour of different DNS
+implementations is expected to be the same.
+Requirements for protocol behaviour of DNS implementations is widely documented
+in the case of 'common' dns messages. The DNS protocol is over 20 years old and
+since its inception, there have been over 40 independent DNS implementations,
+while some implementations have over 20 versions.
+The methodology used to identify individual nameserver implementations is based
+on "borderline" protocol behaviour. The DNS protocol offers a multitude of
+message bits, response types, opcodes, classes, query types and label types in a
+fashion that makes some mutually exclusive while some are not used in a query
+messages at all. Not every implementation offers the full set of features the
+DNS protocol set currently has. Some implementations offer features outside the
+protocol set, and there are implementations that do not conform to standards.
+Also, new features added to - or bugs removed allow for differentiations between
+versions of an implementation.
+ <remote-id type="github">kirei/fpdns</remote-id>