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

3 files changed, 12 insertions, 91 deletions

diff --git a/media-gfx/nvidia-cg-toolkit/ChangeLog b/media-gfx/nvidia-cg-toolkit/ChangeLog
index 6eff27d..750413b 100644
--- a/media-gfx/nvidia-cg-toolkit/ChangeLog
+++ b/media-gfx/nvidia-cg-toolkit/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for media-gfx/nvidia-cg-toolkit
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*nvidia-cg-toolkit-3.0.0000 (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> +nvidia-cg-toolkit-3.0.0000.ebuild :
+  Initial commit of the ebuild.
diff --git a/media-gfx/nvidia-cg-toolkit/Manifest b/media-gfx/nvidia-cg-toolkit/Manifest
index dc05463..f73cf7d 100644
--- a/media-gfx/nvidia-cg-toolkit/Manifest
+++ b/media-gfx/nvidia-cg-toolkit/Manifest
@@ -1,4 +1,5 @@
 DIST Cg-3.0_July2010_x86.tgz 19662219 RMD160 271b758fc59a6eb343ea3ecd0d87295529b2bd17 SHA1 522e47c4cef7ec659503323bbb915adda449f606 SHA256 ce68db5c98bd9b831dee7508edc80a512fed3cacc14b654f08dce04b8087c5c8
 DIST Cg-3.0_July2010_x86_64.tgz 20733994 RMD160 90cee7f0ced3c04bccb384cbce0c6dbdc6b02f0a SHA1 4c71bcda694880ca4c89e145d9e90c3d96897a33 SHA256 5e48ca1a7e52133354aeb8c051cf032f5c712a4c74b58ba8e98044a255f0c49b
 EBUILD nvidia-cg-toolkit-3.0.0000.ebuild 1124 RMD160 3bbe4e3dfd82f3cfc49811025d57744bc30932e2 SHA1 d14c9c0ba696e2fcb41dca816a2e2ab5c35cff6e SHA256 bd2198636b3272fe1bb2850da406ed309df5be5df79c7638ca0b6d0f8461039f
-MISC nvidia-cg-toolkit-3.0.0000.ebuild~ 1246 RMD160 a493d25cfde3cb530a9971c91d16f501a20a1e93 SHA1 7daf3d1374827c0b0c715ac050b2bb4e1d7221c8 SHA256 70fb081e270ac9c75602ae0845182e65a616d8757e4bb8d6edf7b0ce5204c3fb
+MISC ChangeLog 284 RMD160 24b980f4a9e286eb2a5fc8e4456334d94f6b5112 SHA1 fac06bc20d354ff7ce2eb013fd00b4bac3d7e0d1 SHA256 87a2c55162b144cc026989b25483407a1d8c1176422fabdd8d6d9f85ec12a902
+MISC metadata.xml 363 RMD160 c640b825efd0eb007e5b64122dbf9166948cf4ae SHA1 2c06546dd209aa3c0ac88d688b644387da133a87 SHA256 0b51398a901ef4e1901e2d6f2acd7d63bc01e76039a52e85140e7d8b55d9e2c1
diff --git a/media-gfx/nvidia-cg-toolkit/metadata.xml b/media-gfx/nvidia-cg-toolkit/metadata.xml
index 46a44e5..eadd8f9 100644
--- a/media-gfx/nvidia-cg-toolkit/metadata.xml
+++ b/media-gfx/nvidia-cg-toolkit/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>