diff options
author | V3n3RiX <venerix@koprulu.sector> | 2022-10-20 07:59:50 +0100 |
---|---|---|
committer | V3n3RiX <venerix@koprulu.sector> | 2022-10-20 07:59:50 +0100 |
commit | 2eda3a3b8ebdb3fc8552feb6f49e466d3bc8e88c (patch) | |
tree | 69a469da2fa8c3f4920325ac5595300929f5d884 /net-dns/fpdns | |
parent | 9ed0c42eb618229fa6f45e10155ee535e1f605a2 (diff) |
gentoo auto-resync : 20:10:2022 - 07:59:49
Diffstat (limited to 'net-dns/fpdns')
-rw-r--r-- | net-dns/fpdns/Manifest | 2 | ||||
-rw-r--r-- | net-dns/fpdns/metadata.xml | 34 |
2 files changed, 18 insertions, 18 deletions
diff --git a/net-dns/fpdns/Manifest b/net-dns/fpdns/Manifest index 2d56765fec67..cb863af33cd2 100644 --- a/net-dns/fpdns/Manifest +++ b/net-dns/fpdns/Manifest @@ -1,4 +1,4 @@ AUX fpdns-0.10.0_pre20130404.ro-header.patch 1115 BLAKE2B d8042816acce161ba4e19533700151489f3a169fb96a11d4eb44b107818fe0eab87cb916b4e8d5d2a45e22c82693517d069c6e12095b415b352d40384a9040db SHA512 e345037a210103f5202c0dd052952bd2d3889ad53393fc4881ec48810f3e6d39b1b7d2220d259ffda0b85e339bcc4ef9f1ae28023cf84b81a00685c66e116923 DIST fpdns-0.10.0_pre20130404.tar.gz 931723 BLAKE2B cab459afee74ef5d8163a25b98c123b799270e6d3293f155a340ebdbfbc86266fbffa999d31928c9b1a732898b0adf4a49e97469f9ae992a0e38f9478431e84c SHA512 1a4d9c1cb666efa3f48dcca2b5cd04793e92727359652095572b17479f5343479c57d2937f1fff8070c071a2698eda5c4dff981caf86436f184f0b076b0fa0b3 EBUILD fpdns-0.10.0_pre20130404-r1.ebuild 585 BLAKE2B e65b3bcb59605233edf82566bd02b28e858f2398bcc1d6984eb6713b567d9bf450ac976497c07c6d6129c6806e900477c862471eb5799c2a675c85822079d4da SHA512 99ded2a507030ff035b56945576f965473ab9e4ed6fde789dd79808978a96626ee087018c0b600d969d509820ff63eaf8e64bb9c3d96b6d3ff648d74313c1854 -MISC metadata.xml 1421 BLAKE2B aa284dbfc1b37ec2da8254b22242b872198de6a84940075cafc023d25e31a552c150f47b3eeac9d1d57ed6307ba71774733c3dcac5a8d6342a221c77de660086 SHA512 2f174a68b6bdbd47c32645b0faa408b51a2bfaa4869c3e32498aeb9311d7b9d4de7dd598b63858b1b4fef283172728f23beb9ae1812b5937420e96fbe7718388 +MISC metadata.xml 1438 BLAKE2B 048c17c0264b5e2b5709f4da82bc22d3f7a197ba202c9c95f27bfcb0d52e91b87fb1bbae7791d94eefc6f688856e0d6bf311ae712922606f5cb76300b7c05283 SHA512 1f8ca836146892d3ca4cede7547de9c682d1d77f95f77380db4f78f6d7e7472f5d80544b98dc3235f34b2c69b0071ab5e6af03986aae331616fb4bcf10c0e033 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> |