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

3 files changed, 12 insertions, 89 deletions

diff --git a/net-mail/davmail/ChangeLog b/net-mail/davmail/ChangeLog
index 6eff27d..672362b 100644
--- a/net-mail/davmail/ChangeLog
+++ b/net-mail/davmail/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for net-mail/davmail
 # Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
 # $Header: $
 
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*davmail-3.9.1_p1646 (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> +davmail-3.9.1_p1646.ebuild :
+  Initial commit of the ebuild.
diff --git a/net-mail/davmail/Manifest b/net-mail/davmail/Manifest
index 8ee912c..a4439be 100644
--- a/net-mail/davmail/Manifest
+++ b/net-mail/davmail/Manifest
@@ -2,4 +2,5 @@ AUX davmail.desktop 211 RMD160 a0c72ff2427b813d292c706c89878e556b13e2ea SHA1 bd2
 AUX davmail.png 4218 RMD160 1b271ae8e6f85f1550c5140080fb6b7f64799afc SHA1 44fe30922093156f2c594065c59bed7442ec5083 SHA256 b50a1e8d9ac3e20acf88f77d9524f986041282e9f6ae120c78ee64cf6a20df7e
 DIST davmail-linux-x86_64-3.9.1-1646.tgz 6386052 RMD160 a4857788123eb6e3ff5d08378818047b306dcd60 SHA1 5ebe787330d0cd4ca4336110bb36bac029d14a1e SHA256 2c7b85cccc1f7883a01f3ea5b04f6e71f057abcdcdb06f26ed8d129e21c8f4ea
 EBUILD davmail-3.9.1_p1646.ebuild 906 RMD160 f864230d1b2eeb77c0a7307f5f98fbd1a52fc809 SHA1 6a6904d2c59b5f5b91ec41e3573edf63d96aa6e2 SHA256 df4ac1b21dfb8ba5c6003403e6e501469fbc55fde6060737a142067ba26328c5
-MISC davmail-3.9.1_p1646.ebuild~ 931 RMD160 e846ab784504abe58b3da611f087941909ae10fa SHA1 cc25d837af82e26387a833a3ca943e30536d1337 SHA256 1ae361f9f9d803c0928d3689722475314e902bcd5e3450801fa44faeef77557b
+MISC ChangeLog 259 RMD160 f6550e7c92413e9789b381b152f44560d819573b SHA1 0df3571de81add4e2d25820baf8190656d6aecbb SHA256 61815c24e33f550d1aaa6175bd548bc1b42984412e433e5c6606869b3f80d2b7
+MISC metadata.xml 418 RMD160 83e868ddcb65ebc7922f23f374711cb84b846eda SHA1 5263d2c8167ff653051cc85a6fc77b93ede578f6 SHA256 b59331561c72362e2c161175bb46b254d6f223cb98fb54c87b427950dcdc2ef1
diff --git a/net-mail/davmail/metadata.xml b/net-mail/davmail/metadata.xml
index 46a44e5..fede150 100644
--- a/net-mail/davmail/metadata.xml
+++ b/net-mail/davmail/metadata.xml
@@ -1,34 +1,15 @@
 <?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> -->
-<!--
+<longdescription>
+MISSING
+</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>
+  <flag name='menu'>Install a desktop icon</flag>
 </use>
--->
 </pkgmetadata>