summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPetr Vaněk <arkamar@atlas.cz>2022-10-19 09:44:20 +0200
committerSam James <sam@gentoo.org>2022-10-20 04:52:23 +0100
commitdf51218ca65b08225bc66e2faa3001d98d464e30 (patch)
treec789534a51f613f9946f42a6b02686ba8d5ff418 /net-dns/fpdns
parentnet-dns/dnrd: align longdescription opening and closing tags (diff)
downloadgentoo-df51218ca65b08225bc66e2faa3001d98d464e30.tar.gz
gentoo-df51218ca65b08225bc66e2faa3001d98d464e30.tar.bz2
gentoo-df51218ca65b08225bc66e2faa3001d98d464e30.zip
net-dns/fpdns: align longdescription opening and closing tags
Signed-off-by: Petr Vaněk <arkamar@atlas.cz> Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'net-dns/fpdns')
-rw-r--r--net-dns/fpdns/metadata.xml34
1 files changed, 17 insertions, 17 deletions
diff --git a/net-dns/fpdns/metadata.xml b/net-dns/fpdns/metadata.xml
index 7b8047263afb..d6cd618589b3 100644
--- a/net-dns/fpdns/metadata.xml
+++ b/net-dns/fpdns/metadata.xml
@@ -3,26 +3,26 @@
<pkgmetadata>
<!-- maintainer-needed -->
<longdescription>
-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.
+ 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.
+ 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.
+ 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.
-</longdescription>
+ Also, new features added to - or bugs removed allow for differentiations between
+ versions of an implementation.
+ </longdescription>
<upstream>
<remote-id type="github">kirei/fpdns</remote-id>
</upstream>