dev-python/pylint: use consistent indentation for metadata.xml

diff --git a/dev-python/pylint/metadata.xml b/dev-python/pylint/metadata.xml
index 75b5122deeaa7d5522deb9684b57bc9e7ef55040..4fd10546d5c797fb71a979b21c4681a1b762f365 100644 (file)
--- a/dev-python/pylint/metadata.xml
+++ b/dev-python/pylint/metadata.xml
@@ -5,15 +5,17 @@
     <email>python@gentoo.org</email>
     <name>Python</name>
   </maintainer>
-  <longdescription lang="en">Pylint is a Python source code analyzer which looks for programming
-               errors, helps enforcing a coding standard and sniffs for some code
-               smells (as defined in Martin Fowler's Refactoring book).
-               Pylint can be seen as another PyChecker since nearly all tests you can
-               do with PyChecker can also be done with Pylint. However, Pylint offers
-               some more features, like checking length of lines of code, checking if
-               variable names are well-formed according to your coding standard, or
-               checking if declared interfaces are truly implemented, and much more.
-               Additionally, it is possible to write plugins to add your own checks.</longdescription>
+  <longdescription lang="en">
+    Pylint is a Python source code analyzer which looks for programming errors,
+    helps enforcing a coding standard and sniffs for some code smells (as
+    defined in Martin Fowler's Refactoring book). Pylint can be seen as
+    another PyChecker since nearly all tests you can do with PyChecker can also
+    be done with Pylint. However, Pylint offers some more features, like
+    checking length of lines of code, checking if variable names are
+    well-formed according to your coding standard, or checking if declared
+    interfaces are truly implemented, and much more. Additionally, it is
+    possible to write plugins to add your own checks.
+  </longdescription>
   <upstream>
     <remote-id type="pypi">pylint</remote-id>
     <remote-id type="github">pycqa/pylint</remote-id>