Everything digested. ChangeLogs and metadata.xml files will be updated tomorrow.

9 files changed, 38 insertions, 248 deletions

diff --git a/games-strategy/freeorion/ChangeLog b/games-strategy/freeorion/ChangeLog
index 6eff27d..ae2ba8f 100644
--- a/games-strategy/freeorion/ChangeLog
+++ b/games-strategy/freeorion/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for games-strategy/freeorion
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*freeorion-9999-r5 (27 Mar 2011)
 
-  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2 :
-  Initial import.  Ebuild submitted by submitter_name <submitter_email>.
-  Note that the "changed_file" listing is optional if you are simply bumping
-  the rev of the ebuild and are only making changes to the .ebuild file
-  itself.  Also note that we now have a single unified paragraph rather than
-  having the first line separated from the rest by a newline.  Everything
-  should be in one block like this. (note by drobbins, 16 Jul 2002)
-
-  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
-  an earlier ChangeLog entry.
-
--- Explanation of ChangeLog format:
-
-  ***************************************************************************
-  THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all
-  changes made to a set of ebuilds. That means that the most recent ChangeLog
-  entry *always* goes at the top of the file. More explanation below.
-  ***************************************************************************
-
-  ***************************************************************************
-  ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this
-  format and organize all changes under the "correct" "*" entry. This is not
-  correct. However, rather than making a concerted effort to fix these
-  ChangeLogs, we should spend our energy defining a comprehensive and strict
-  XML-based ChangeLog format which we then migrate to. But for any entries to
-  any ChangeLog that *you* make, please make sure to always add entries to the
-  top of the file like a good boy/girl. Even do this if it's clear that you're
-  adding an entry to a b0rked ChangeLog.
-  ***************************************************************************
-
-  This changelog is targeted to users. This means that the comments should be
-  well explained and written in clean English.
-
-  Every new version or revision of the package should be marked by a '*'
-  separator line as above to indicate where in the chronology it was first
-  added to our CVS tree. Any changes since the last revision, really _any
-  changes at all_ have to be added to the top of the file, underneath the
-  initial copyright and cvs header comments, in exactly the same format as this
-  comment. If you are modifying older ebuilds, simply note them as changed
-  files and add your entry to the top of the ChangeLog. Resist the temptation
-  to "organize" your ChangeLog entries by placing them under the "correct" "*"
-  entries -- this isn't the purpose of the "*" entries.
-
-  This means that you start with header line that has the following format,
-  indented two spaces:
-
-  DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
-  explanation should follow. It should be indented and wrapped at a line width
-  of 80 characters.  The changed_files can be omitted if they are obvious; for
-  example, if you are only modifying the .ebuild file and committing a new rev
-  of a package.  Any details about what exactly changed in the code should be
-  added as a message when the changes are committed to cvs, not in this file.
-
--- A word regarding credit:
-
-  Please add credit information ("ebuild submitted by ...", "patch submitted
-  by ...") to the ChangeLog. Do not add this information to the ebuilds
-  themselves.
-
-  And remember: Give credit where credit is due. We're all doing this for
-  free, so the best we can hope (and expect!) to receive is credit.
+  27 Mar 2011; Sven Eden <sven.eden@gmx.de> +freeorion-9999-r5.ebuild :
+  Initial commit of the ebuild.
diff --git a/games-strategy/freeorion/Manifest b/games-strategy/freeorion/Manifest
index 288b330..fdb777a 100644
--- a/games-strategy/freeorion/Manifest
+++ b/games-strategy/freeorion/Manifest
@@ -1,3 +1,3 @@
 EBUILD freeorion-9999-r5.ebuild 2829 RMD160 ddbb4bb5ac6b03e36dbcbe8fba9f489d3286cbd8 SHA1 dbdd4eb8e819b9262ae145155e481a3794645a3b SHA256 4a550b9a6a11c38f58e26030c45ae9d6093e65b8d94b13feec321548933fe566
-MISC freeorion-9999-r5.ebuild~ 2828 RMD160 f03d3a3e751a11d982f413db6275e05206dcda81 SHA1 460f18911821a0bd66ff2a489833815f97db85d4 SHA256 0235b077a9290b4f357836e775acbbc9b0b11062de836e557a69081382a1670d
-MISC metadata.xml 289 RMD160 1ddd83f6157c2a67fe8d507cdfaa68f4ca00c634 SHA1 9c3f17b83bfd9097e844e7d5e6102a6179ec6350 SHA256 0a23813a0270aa7139c3c527e15b1b367a1509f2a98903aec2fe2d2496bacf99
+MISC ChangeLog 263 RMD160 a660340eb32fb385e9e81cf57355f938ba542455 SHA1 114a9c739072f2417238177b69264a55f00d5cf1 SHA256 82618dc1d05ec2d63ae49a4c9d30d231b29fa2e76064d4a3e2c1d699384f0a17
+MISC metadata.xml 482 RMD160 4d1a06c8b3833acbcf43d0b56a0c0ff3ba938fde SHA1 fdcead5b8dc226ee4bc44e19642fdec006831c2d SHA256 d440736d71b8eaac1b5a2a5171274171e7b5bbbcc6d4b8d2c14fd37c36e51a96
diff --git a/games-strategy/freeorion/metadata.xml b/games-strategy/freeorion/metadata.xml
index a52a84c..b1af44c 100644
--- a/games-strategy/freeorion/metadata.xml
+++ b/games-strategy/freeorion/metadata.xml
@@ -1,7 +1,14 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-	<herd>playboys</herd>
+<herd>no-herd</herd>
+<maintainer>
+  <email>sven.eden@gmx.de</email>
+  <description>The creator of this ebuild, but not the official maintainer</description>
+</maintainer>
+<longdescription>
+MISSING
+</longdescription>
   <use>
     <flag name="xml">Do all serialization using xml archives. Otherwise, binary archives will be used.</flag>
   </use>
diff --git a/games-strategy/glfrontier/ChangeLog b/games-strategy/glfrontier/ChangeLog
index 6eff27d..74e6ac2 100644
--- a/games-strategy/glfrontier/ChangeLog
+++ b/games-strategy/glfrontier/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for games-strategy/glfrontier
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*glfrontier-20060623-r2 (27 Mar 2011)
 
-  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2 :
-  Initial import.  Ebuild submitted by submitter_name <submitter_email>.
-  Note that the "changed_file" listing is optional if you are simply bumping
-  the rev of the ebuild and are only making changes to the .ebuild file
-  itself.  Also note that we now have a single unified paragraph rather than
-  having the first line separated from the rest by a newline.  Everything
-  should be in one block like this. (note by drobbins, 16 Jul 2002)
-
-  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
-  an earlier ChangeLog entry.
-
--- Explanation of ChangeLog format:
-
-  ***************************************************************************
-  THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all
-  changes made to a set of ebuilds. That means that the most recent ChangeLog
-  entry *always* goes at the top of the file. More explanation below.
-  ***************************************************************************
-
-  ***************************************************************************
-  ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this
-  format and organize all changes under the "correct" "*" entry. This is not
-  correct. However, rather than making a concerted effort to fix these
-  ChangeLogs, we should spend our energy defining a comprehensive and strict
-  XML-based ChangeLog format which we then migrate to. But for any entries to
-  any ChangeLog that *you* make, please make sure to always add entries to the
-  top of the file like a good boy/girl. Even do this if it's clear that you're
-  adding an entry to a b0rked ChangeLog.
-  ***************************************************************************
-
-  This changelog is targeted to users. This means that the comments should be
-  well explained and written in clean English.
-
-  Every new version or revision of the package should be marked by a '*'
-  separator line as above to indicate where in the chronology it was first
-  added to our CVS tree. Any changes since the last revision, really _any
-  changes at all_ have to be added to the top of the file, underneath the
-  initial copyright and cvs header comments, in exactly the same format as this
-  comment. If you are modifying older ebuilds, simply note them as changed
-  files and add your entry to the top of the ChangeLog. Resist the temptation
-  to "organize" your ChangeLog entries by placing them under the "correct" "*"
-  entries -- this isn't the purpose of the "*" entries.
-
-  This means that you start with header line that has the following format,
-  indented two spaces:
-
-  DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
-  explanation should follow. It should be indented and wrapped at a line width
-  of 80 characters.  The changed_files can be omitted if they are obvious; for
-  example, if you are only modifying the .ebuild file and committing a new rev
-  of a package.  Any details about what exactly changed in the code should be
-  added as a message when the changes are committed to cvs, not in this file.
-
--- A word regarding credit:
-
-  Please add credit information ("ebuild submitted by ...", "patch submitted
-  by ...") to the ChangeLog. Do not add this information to the ebuilds
-  themselves.
-
-  And remember: Give credit where credit is due. We're all doing this for
-  free, so the best we can hope (and expect!) to receive is credit.
+  27 Mar 2011; Sven Eden <sven.eden@gmx.de> +glfrontier-20060623-r2.ebuild :
+  Initial commit of the ebuild.
diff --git a/games-strategy/glfrontier/Manifest b/games-strategy/glfrontier/Manifest
index 7534a95..c8217b5 100644
--- a/games-strategy/glfrontier/Manifest
+++ b/games-strategy/glfrontier/Manifest
@@ -1,4 +1,5 @@
 DIST frontvm-audio-20060222.tar.bz2 4623648 RMD160 2261dbcdcff0882d1c1870af41b16bbe967c32ea SHA1 ba7bab4235f0ba09b7d4b801ae55ead04ae61da0 SHA256 e759e587047abd6f041aea4ef339e404b3ca5a6407acf65084a2af79a75ceb87
 DIST frontvm3-20060623.tar.bz2 426463 RMD160 0c6f0c25cb1fa048aa9be240e37386c9d2e1e3d5 SHA1 5f046cf2428444c0316afcb3628f6747c4493bd1 SHA256 9b6c04e8dad75bea11cce459515c7d5983276e23dba4a4764f1084d4810c0afb
 EBUILD glfrontier-20060623-r2.ebuild 1110 RMD160 a6dfbc404d1b788909ae81d977854182c92153a4 SHA1 000263db8f9452ac6fe1d808b90387bad1c72fbd SHA256 98b4006fc735d1cbf3e8044a21691b28d924c8680f9824d81729a31df63ac380
-MISC glfrontier-20060623-r2.ebuild~ 1107 RMD160 f54facbfbddc7a5a8ceec827939bb93c34c46bdd SHA1 b56eadd2f25aafb5e84d413986fdf95d8cc61897 SHA256 ff512b70bdf46c56970909cff15a82a9904d863cf63f6a6d77c212e4e36f164c
+MISC ChangeLog 274 RMD160 b3a2b44923ab4eb7d55275e0e915f28bec5b16e0 SHA1 a0a4024e5fc08904b45e7e96dc277ebc2f516101 SHA256 0e297975f43139e81a293bce99b96d9c85de75d307bb22b82cc87e746ac79cff
+MISC metadata.xml 363 RMD160 c640b825efd0eb007e5b64122dbf9166948cf4ae SHA1 2c06546dd209aa3c0ac88d688b644387da133a87 SHA256 0b51398a901ef4e1901e2d6f2acd7d63bc01e76039a52e85140e7d8b55d9e2c1
diff --git a/games-strategy/glfrontier/metadata.xml b/games-strategy/glfrontier/metadata.xml
index 46a44e5..eadd8f9 100644
--- a/games-strategy/glfrontier/metadata.xml
+++ b/games-strategy/glfrontier/metadata.xml
@@ -1,34 +1,13 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<!-- 
-$Header: /var/cvsroot/gentoo-x86/skel.metadata.xml,v 1.18 2008/07/28 19:27:05 cardoe Exp $
-
-This is the example metadata file.
-The root element of this file is <pkgmetadata>. Within this element a 
-number of subelements are allowed: herd, maintainer, and 
-longdescription. herd is a required subelement.
-
-For a full description look at:
-http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4
-
-
-Before committing, please remove the comments from this file. They are 
-not relevant for general metadata.xml files.
--->
 <pkgmetadata>
 <herd>no-herd</herd>
 <maintainer>
-  <email>@gentoo.org</email>
-<!--  <description>Description of the maintainership</description> -->
+  <email>sven.eden@gmx.de</email>
+  <description>The creator of this ebuild, but not the official maintainer</description>
 </maintainer>
-<!-- <longdescription>Long description of the package</longdescription> -->
-<!--
-<use>
-  <flag name='flag'>Description of how USE='flag' affects this package</flag>
-  <flag name='userland_GNU'>Description of how USERLAND='GNU' affects this
-	  package</flag>
-  <flag name='aspell'>Uses <pkg>app-text/aspell</pkg> for spell checking.
-	  Requires an installed dictionary from <cat>app-dicts</cat></flag>
-</use>
--->
+<longdescription>
+MISSING
+</longdescription>
+<use />
 </pkgmetadata>
diff --git a/games-strategy/seven-kingdoms/ChangeLog b/games-strategy/seven-kingdoms/ChangeLog
index 6eff27d..3b88f96 100644
--- a/games-strategy/seven-kingdoms/ChangeLog
+++ b/games-strategy/seven-kingdoms/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for games-strategy/seven-kingdoms
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*seven-kingdoms-2.14.3-r1 (27 Mar 2011)
 
-  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2 :
-  Initial import.  Ebuild submitted by submitter_name <submitter_email>.
-  Note that the "changed_file" listing is optional if you are simply bumping
-  the rev of the ebuild and are only making changes to the .ebuild file
-  itself.  Also note that we now have a single unified paragraph rather than
-  having the first line separated from the rest by a newline.  Everything
-  should be in one block like this. (note by drobbins, 16 Jul 2002)
-
-  DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
-  an earlier ChangeLog entry.
-
--- Explanation of ChangeLog format:
-
-  ***************************************************************************
-  THIS IS IMPORTANT: The ChangeLog format is a *chronological* account of all
-  changes made to a set of ebuilds. That means that the most recent ChangeLog
-  entry *always* goes at the top of the file. More explanation below.
-  ***************************************************************************
-
-  ***************************************************************************
-  ANOTHER IMPORTANT NOTE: There are some ChangeLogs that don't follow this
-  format and organize all changes under the "correct" "*" entry. This is not
-  correct. However, rather than making a concerted effort to fix these
-  ChangeLogs, we should spend our energy defining a comprehensive and strict
-  XML-based ChangeLog format which we then migrate to. But for any entries to
-  any ChangeLog that *you* make, please make sure to always add entries to the
-  top of the file like a good boy/girl. Even do this if it's clear that you're
-  adding an entry to a b0rked ChangeLog.
-  ***************************************************************************
-
-  This changelog is targeted to users. This means that the comments should be
-  well explained and written in clean English.
-
-  Every new version or revision of the package should be marked by a '*'
-  separator line as above to indicate where in the chronology it was first
-  added to our CVS tree. Any changes since the last revision, really _any
-  changes at all_ have to be added to the top of the file, underneath the
-  initial copyright and cvs header comments, in exactly the same format as this
-  comment. If you are modifying older ebuilds, simply note them as changed
-  files and add your entry to the top of the ChangeLog. Resist the temptation
-  to "organize" your ChangeLog entries by placing them under the "correct" "*"
-  entries -- this isn't the purpose of the "*" entries.
-
-  This means that you start with header line that has the following format,
-  indented two spaces:
-
-  DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
-  explanation should follow. It should be indented and wrapped at a line width
-  of 80 characters.  The changed_files can be omitted if they are obvious; for
-  example, if you are only modifying the .ebuild file and committing a new rev
-  of a package.  Any details about what exactly changed in the code should be
-  added as a message when the changes are committed to cvs, not in this file.
-
--- A word regarding credit:
-
-  Please add credit information ("ebuild submitted by ...", "patch submitted
-  by ...") to the ChangeLog. Do not add this information to the ebuilds
-  themselves.
-
-  And remember: Give credit where credit is due. We're all doing this for
-  free, so the best we can hope (and expect!) to receive is credit.
+  27 Mar 2011; Sven Eden <sven.eden@gmx.de> +seven-kingdoms-2.14.3-r1.ebuild :
+  Initial commit of the ebuild.
diff --git a/games-strategy/seven-kingdoms/Manifest b/games-strategy/seven-kingdoms/Manifest
index b90ab1a..3205d6b 100644
--- a/games-strategy/seven-kingdoms/Manifest
+++ b/games-strategy/seven-kingdoms/Manifest
@@ -2,4 +2,5 @@ AUX 7kaa.png 2679 RMD160 31f4cca441e3bfd4b19fd8a735d97891d081dda9 SHA1 236cf22e8
 DIST 7kaa-data-2.13.tar.bz2 37107989 RMD160 a5e3ebbdd2c56269ffff6655fb2d14c4f900b516 SHA1 1283c5fa8545654fc45de39229afb6c7149a39d0 SHA256 b02052502b382dd78fdabaef0b378c0a3e85d91fe21fb067d47d1ebfe02d4294
 DIST 7kaa-source-2.14.3.tar.bz2 1181479 RMD160 84bcc723a63f684047962a4bb03a85e07a9ad946 SHA1 0926383fc32ad0b0af780edf575fb170a00c8d30 SHA256 9d3ba6e4d72495cf83eec922714f818c68974e9ad62e934608676d93a4b48aef
 EBUILD seven-kingdoms-2.14.3-r1.ebuild 2723 RMD160 257895345e6cd38ba70e4bba1ba0520bfca8c563 SHA1 3eca98fedd983ca7c0a0e7ad8e7b8b6dcd2e1a16 SHA256 6911b4850a295693fb641bd2fb91f2e02747e741480707636806db5d05fc8b47
-MISC seven-kingdoms-2.14.3-r1.ebuild~ 2722 RMD160 c27b0cedef8bf906179b555eb4332a6330c80d5d SHA1 12686be8226cb388c72117df284de33e244f78fe SHA256 24425171288da33277e5a8ffcbfce4bff4fb9c3c954dd2af099610898288cac2
+MISC ChangeLog 282 RMD160 e98fdc5d60f029058f39f26a3d053022c2c5b8f7 SHA1 b5683c983af76ee5196873cb7892552c09f9ee44 SHA256 b017635a57d30ee5a04ba86e3f444f1b8c6451564f378a9fce2c6657c4f3b063
+MISC metadata.xml 363 RMD160 c640b825efd0eb007e5b64122dbf9166948cf4ae SHA1 2c06546dd209aa3c0ac88d688b644387da133a87 SHA256 0b51398a901ef4e1901e2d6f2acd7d63bc01e76039a52e85140e7d8b55d9e2c1
diff --git a/games-strategy/seven-kingdoms/metadata.xml b/games-strategy/seven-kingdoms/metadata.xml
index 46a44e5..eadd8f9 100644
--- a/games-strategy/seven-kingdoms/metadata.xml
+++ b/games-strategy/seven-kingdoms/metadata.xml
@@ -1,34 +1,13 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<!-- 
-$Header: /var/cvsroot/gentoo-x86/skel.metadata.xml,v 1.18 2008/07/28 19:27:05 cardoe Exp $
-
-This is the example metadata file.
-The root element of this file is <pkgmetadata>. Within this element a 
-number of subelements are allowed: herd, maintainer, and 
-longdescription. herd is a required subelement.
-
-For a full description look at:
-http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=4
-
-
-Before committing, please remove the comments from this file. They are 
-not relevant for general metadata.xml files.
--->
 <pkgmetadata>
 <herd>no-herd</herd>
 <maintainer>
-  <email>@gentoo.org</email>
-<!--  <description>Description of the maintainership</description> -->
+  <email>sven.eden@gmx.de</email>
+  <description>The creator of this ebuild, but not the official maintainer</description>
 </maintainer>
-<!-- <longdescription>Long description of the package</longdescription> -->
-<!--
-<use>
-  <flag name='flag'>Description of how USE='flag' affects this package</flag>
-  <flag name='userland_GNU'>Description of how USERLAND='GNU' affects this
-	  package</flag>
-  <flag name='aspell'>Uses <pkg>app-text/aspell</pkg> for spell checking.
-	  Requires an installed dictionary from <cat>app-dicts</cat></flag>
-</use>
--->
+<longdescription>
+MISSING
+</longdescription>
+<use />
 </pkgmetadata>