Picked up maintenance of valgrind

diff --git a/dev-util/valgrind/ChangeLog b/dev-util/valgrind/ChangeLog
index 7b149043616cb738e32d02e1fa5bd42d47002e0e..c428071518e1745fe7a6b7969bc3e8ce77162185 100644 (file)
--- a/dev-util/valgrind/ChangeLog
+++ b/dev-util/valgrind/ChangeLog
@@ -1,6 +1,9 @@
 # ChangeLog for dev-util/valgrind
 # Copyright 2000-2004 Gentoo Foundation; Distributed under the GPL v2
-# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/ChangeLog,v 1.38 2004/09/24 01:44:17 caleb Exp $
+# $Header: /var/cvsroot/gentoo-x86/dev-util/valgrind/ChangeLog,v 1.39 2004/10/28 19:33:05 griffon26 Exp $
+
+  28 Oct 2004; Maurice van der Pot <griffon26@gentoo.org> metadata.xml:
+  Taken up maintenance of valgrind.
 
   23 Sep 2004; Caleb Tennis <caleb@gentoo.org> valgrind-2.2.0.ebuild:
   Marking x86 stable

diff --git a/dev-util/valgrind/Manifest b/dev-util/valgrind/Manifest
index c6d0a1e20fa4494f26ca339acfc50cf8f598246b..3dde4e38b14976db6610e1a3a7796af82b928968 100644 (file)
--- a/dev-util/valgrind/Manifest
+++ b/dev-util/valgrind/Manifest
@@ -1,17 +1,27 @@
+-----BEGIN PGP SIGNED MESSAGE-----
+Hash: SHA1
+
 MD5 87ba65472b071a1a696226f0e36937d5 valgrind-2.0.0.ebuild 1173
-MD5 36b52cc7f792a5f6944af5e3488fc3cd valgrind-2.1.1-r1.ebuild 1140
 MD5 f07a6833b689f5e27ddc6f11cce48fbb valgrind-2.1.0.ebuild 1018
+MD5 36b52cc7f792a5f6944af5e3488fc3cd valgrind-2.1.1-r1.ebuild 1140
+MD5 a0b171b6dab7cb44a9eab9bf70738b7c valgrind-2.1.1.ebuild 926
 MD5 74af16c4f9ed08248153f39e9181c7be valgrind-2.1.2.ebuild 1099
+MD5 799f0b61a3a686b4074bd61acc572c5c metadata.xml 1003
+MD5 ae6e19ad890434e670e098263cd07f2c ChangeLog 1886
 MD5 f89777a4817a47cc876c1a51cf1b2298 valgrind-2.2.0.ebuild 1384
-MD5 ddda30e081c28534436faadc7ee6b6cc ChangeLog 1773
-MD5 a0b171b6dab7cb44a9eab9bf70738b7c valgrind-2.1.1.ebuild 926
-MD5 f4b910c589410d7ec055b9bda08a32b1 metadata.xml 1001
-MD5 96f4ea73f94e4b969cd764574aeef978 files/valgrind-2.1.2-kernel-headers.patch 826
-MD5 95845f5c26fd00027163547288c17e54 files/valgrind-configure.in-2.6.diff 336
 MD5 286d10f4514e8a85360ce6ba5654ae93 files/digest-valgrind-2.0.0 67
 MD5 a69fe5652a8ca5fb1d04521fe0c56850 files/digest-valgrind-2.1.0 138
 MD5 f50184c09d0376e66b1b79d0b45e94c2 files/digest-valgrind-2.1.1 67
+MD5 f50184c09d0376e66b1b79d0b45e94c2 files/digest-valgrind-2.1.1-r1 67
 MD5 dd98566219aee764f036fae263b1ce61 files/digest-valgrind-2.1.2 67
-MD5 26192577445b467e528408118f7ee6ec files/digest-valgrind-2.2.0 139
 MD5 1ba26123d6543d9b4faa808595fbb5b8 files/valgrind-2.1.1-pic.patch 8338
-MD5 f50184c09d0376e66b1b79d0b45e94c2 files/digest-valgrind-2.1.1-r1 67
+MD5 96f4ea73f94e4b969cd764574aeef978 files/valgrind-2.1.2-kernel-headers.patch 826
+MD5 95845f5c26fd00027163547288c17e54 files/valgrind-configure.in-2.6.diff 336
+MD5 26192577445b467e528408118f7ee6ec files/digest-valgrind-2.2.0 139
+-----BEGIN PGP SIGNATURE-----
+Version: GnuPG v1.2.6 (GNU/Linux)
+
+iD8DBQFBgUl6MGnpIbeahxwRAj2hAJ9+l+lF6HBdSv+P5JYDPnCAQix0GACgrZmn
+X5p09MmDSLHlXugFIHa2+BI=
+=m/m+
+-----END PGP SIGNATURE-----

diff --git a/dev-util/valgrind/metadata.xml b/dev-util/valgrind/metadata.xml
index 14b5556b418f871fa05dc17073db78747ae274c5..76ea83251e3c949627f97eef28f49f77c667a31b 100644 (file)
--- a/dev-util/valgrind/metadata.xml
+++ b/dev-util/valgrind/metadata.xml
@@ -2,25 +2,23 @@
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
        <herd>no-herd</herd>
-<!--
        <maintainer>
-               <description>Package has no maintainer</description>
+               <email>griffon26@gentoo.org</email>
        </maintainer>
--->
-<longdescription>
-Valgrind is a GPL'd tool to help you find memory-management problems
-in your programs. When a program is run under Valgrind's supervision,
-all reads and writes of memory are checked, and calls to
-malloc/new/free/delete are intercepted. As a result, Valgrind can
-detect problems such as
+       <longdescription>
+               Valgrind is a GPL'd tool to help you find memory-management problems
+               in your programs. When a program is run under Valgrind's supervision,
+               all reads and writes of memory are checked, and calls to
+               malloc/new/free/delete are intercepted. As a result, Valgrind can
+               detect problems such as
 
-- Use of uninitialised memory
-- Reading/writing memory after it has been free'd
-- Reading/writing off the end of malloc'd blocks
-- Reading/writing inappropriate areas on the stack
-- Memory leaks -- where pointers to malloc'd blocks are lost forever
-- Passing of uninitialised and/or unaddressible memory to system calls
-- Mismatched use of malloc/new/new [] vs free/delete/delete []
-- Some abuses of the POSIX Pthreads API
-</longdescription>
+               - Use of uninitialised memory
+               - Reading/writing memory after it has been free'd
+               - Reading/writing off the end of malloc'd blocks
+               - Reading/writing inappropriate areas on the stack
+               - Memory leaks -- where pointers to malloc'd blocks are lost forever
+               - Passing of uninitialised and/or unaddressible memory to system calls
+               - Mismatched use of malloc/new/new [] vs free/delete/delete []
+               - Some abuses of the POSIX Pthreads API
+       </longdescription>
 </pkgmetadata>