summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSven Eden <sven.eden@gmx.de>2011-03-29 17:38:00 +0200
committerSven Eden <sven.eden@gmx.de>2011-03-29 17:38:00 +0200
commitff56ab67a56972d1f766a3bb02278b748982e998 (patch)
treede867614c783a2e52d28dd81f1fbd7920953610b
parentSome cleanups and additions (diff)
downloadseden-ff56ab67a56972d1f766a3bb02278b748982e998.tar.gz
seden-ff56ab67a56972d1f766a3bb02278b748982e998.tar.bz2
seden-ff56ab67a56972d1f766a3bb02278b748982e998.zip
Everything digested. ChangeLogs and metadata.xml files will be updated tomorrow.
-rw-r--r--app-emulation/puae/Manifest6
-rw-r--r--app-emulation/winetricks/Manifest5
-rw-r--r--app-office/unoconv/ChangeLog67
-rw-r--r--app-office/unoconv/Manifest3
-rw-r--r--app-office/unoconv/metadata.xml33
-rw-r--r--dev-games/cel/ChangeLog68
-rw-r--r--dev-games/cel/Manifest4
-rw-r--r--dev-games/cel/metadata.xml30
-rw-r--r--dev-games/crystalspace/ChangeLog68
-rw-r--r--dev-games/crystalspace/Manifest4
-rw-r--r--dev-games/crystalspace/metadata.xml32
-rw-r--r--dev-games/gigi/ChangeLog67
-rw-r--r--dev-games/gigi/Manifest4
-rw-r--r--dev-games/gigi/metadata.xml7
-rw-r--r--games-roguelike/tomenet/ChangeLog66
-rw-r--r--games-roguelike/tomenet/Manifest3
-rw-r--r--games-roguelike/tomenet/metadata.xml30
-rw-r--r--games-strategy/freeorion/ChangeLog67
-rw-r--r--games-strategy/freeorion/Manifest4
-rw-r--r--games-strategy/freeorion/metadata.xml9
-rw-r--r--games-strategy/glfrontier/ChangeLog67
-rw-r--r--games-strategy/glfrontier/Manifest3
-rw-r--r--games-strategy/glfrontier/metadata.xml33
-rw-r--r--games-strategy/seven-kingdoms/ChangeLog67
-rw-r--r--games-strategy/seven-kingdoms/Manifest3
-rw-r--r--games-strategy/seven-kingdoms/metadata.xml33
-rw-r--r--media-gfx/nvidia-cg-toolkit/ChangeLog67
-rw-r--r--media-gfx/nvidia-cg-toolkit/Manifest3
-rw-r--r--media-gfx/nvidia-cg-toolkit/metadata.xml33
-rw-r--r--media-libs/jbig2enc/ChangeLog67
-rw-r--r--media-libs/jbig2enc/Manifest3
-rw-r--r--media-libs/jbig2enc/metadata.xml33
-rw-r--r--media-libs/leptonica/ChangeLog67
-rw-r--r--media-libs/leptonica/Manifest3
-rw-r--r--media-libs/leptonica/metadata.xml33
-rw-r--r--net-mail/davmail/ChangeLog67
-rw-r--r--net-mail/davmail/Manifest3
-rw-r--r--net-mail/davmail/metadata.xml31
-rw-r--r--sys-power/cpufreqd/ChangeLog69
-rw-r--r--sys-power/cpufreqd/Manifest3
-rw-r--r--sys-power/cpufreqd/metadata.xml38
-rw-r--r--www-apps/dotproject/ChangeLog68
-rw-r--r--www-apps/dotproject/Manifest3
-rw-r--r--www-apps/dotproject/metadata.xml31
44 files changed, 179 insertions, 1226 deletions
diff --git a/app-emulation/puae/Manifest b/app-emulation/puae/Manifest
index 9ed0096..54c2190 100644
--- a/app-emulation/puae/Manifest
+++ b/app-emulation/puae/Manifest
@@ -1,3 +1,3 @@
-EBUILD puae-2.3.1_pre9999.ebuild 7299 RMD160 fb69d409717e7edaf00d617a66381fbfb9ce5e1e SHA1 28d99c948ecf1f66a139cdc57bb037e3f53330b5 SHA256 db2cc7cc6b34ded9b9e57605644ee7ab84af5cfa0beed241ad271400696f752f
-MISC metadata.xml 2409 RMD160 aa18392a318f6979d0662ad3d99895c379fb8ce7 SHA1 7f01ca258971a3ba17c9d247109c86d6e70e3fe4 SHA256 892ce67fe34e9c6700dd9e97a903c8dcdd15fd7095b563a9fc75b1f527312890
-MISC puae-2.3.1_pre9999.ebuild~ 7299 RMD160 fb69d409717e7edaf00d617a66381fbfb9ce5e1e SHA1 28d99c948ecf1f66a139cdc57bb037e3f53330b5 SHA256 db2cc7cc6b34ded9b9e57605644ee7ab84af5cfa0beed241ad271400696f752f
+EBUILD puae-2.3.2_pre9999.ebuild 7299 RMD160 fb69d409717e7edaf00d617a66381fbfb9ce5e1e SHA1 28d99c948ecf1f66a139cdc57bb037e3f53330b5 SHA256 db2cc7cc6b34ded9b9e57605644ee7ab84af5cfa0beed241ad271400696f752f
+MISC ChangeLog 591 RMD160 bf966a386fe430c6c856ed78501dbe909207c53a SHA1 3361d055a2526dd4fa53e64b3688951cc8e42e4a SHA256 7f3cc6da4efb60ebf48bd3e5fbf844117067f837f46b68be516205c2cf46f7a3
+MISC metadata.xml 2643 RMD160 1ca246d22ebf49473428fabd6c1a90afb2d79f78 SHA1 add1c4f16b996324195781410d87387f028fc195 SHA256 8ec7853257496220eed3d5c8d3d7ec11c5199a3f5c1ca55c5432b9d4e5475e26
diff --git a/app-emulation/winetricks/Manifest b/app-emulation/winetricks/Manifest
index 6ff8f9b..ca9b9d1 100644
--- a/app-emulation/winetricks/Manifest
+++ b/app-emulation/winetricks/Manifest
@@ -1,2 +1,3 @@
-EBUILD winetricks-9999.ebuild 596 RMD160 c90da7a3e5d7d00c4d35680e67d34daf16697d63 SHA1 faac7283d4799972a317d2115a67194717c82536 SHA256 636f4abb800c480112a9c2dbff5e358c8ed22f4b7bf795d7c84db41a2dd8b7de
-MISC winetricks-9999.ebuild~ 595 RMD160 b472b2260e8fea12cbf1034a0106adcd8d30829e SHA1 45c7f6f91fb27f0e04db41ce29206171df0e0ec7 SHA256 afbc1919f097d69b57a79d80bdf68339088914e658bf8eefaa476d6911996b11
+EBUILD winetricks-9999-r1.ebuild 600 RMD160 84aab2a225f7b1d44c63fc2ba1360b4809b168fd SHA1 fdc4541a428d61490fcbc3754ef95fd055fadd1f SHA256 b71eb682a0c11bca86025f5965b6ed16c7c6791861c2b3eaa0f61b04b7e5e66b
+MISC ChangeLog 594 RMD160 502d93af9feb28dba7855d95c2bcab2ce2d3195e SHA1 39148f115eaf598459b32f314d6be09656383e58 SHA256 780f464e5318116cdea8b6306258710398164f1f2598182d9544d841f529d901
+MISC metadata.xml 920 RMD160 8222dd697c38f0cdb7646eac5dfbf464b28da16e SHA1 ced5e70ea3cfafbaedbfa5cc7158407908665bda SHA256 9df23a6c60e62941a9146471a92b34d04600ef40694ff29bc8ac947011ae07d8
diff --git a/app-office/unoconv/ChangeLog b/app-office/unoconv/ChangeLog
index 6eff27d..6d02ba8 100644
--- a/app-office/unoconv/ChangeLog
+++ b/app-office/unoconv/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for app-office/unoconv
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*unoconv-0.4 (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> +unoconv-0.4.ebuild : Initial
+ release via seden overlay.
diff --git a/app-office/unoconv/Manifest b/app-office/unoconv/Manifest
index 2db2f46..8c47d4d 100644
--- a/app-office/unoconv/Manifest
+++ b/app-office/unoconv/Manifest
@@ -1,3 +1,4 @@
DIST unoconv-0.4.tar.bz2 63171 RMD160 8b05e181e460dedb8d8c692b4f0e3abd4a23afe4 SHA1 e06a8f6d921ecaecc0968ba92dd7afd5af67a32d SHA256 27711728c19b7b71d94b010540e7648dc72ab6190cc4155c5d8be4dd7f46e48c
EBUILD unoconv-0.4.ebuild 695 RMD160 e655017a2bd566580c99239c7ac63982744af170 SHA1 27911e787305ef9c6fb5f941be2f64e9189771fb SHA256 74298ce9652f60129d09d18d864100b58e30250cde73b775a115ac99ff027068
-MISC unoconv-0.4.ebuild~ 788 RMD160 45e666af8cf20f7218ce075c8103817ac1a69ae1 SHA1 29afbf4ad5e775b93121e462de14bea2ef34fb91 SHA256 cda851f48a7d98d012f5c7f269eeb60e8e408aeefeb97ac3ef6a2272d8a4f365
+MISC ChangeLog 250 RMD160 5ea2e13349ad394739db11ebf03bf0c49831a8c9 SHA1 23653028cc45f032fa7110009d38094528f675d5 SHA256 22b45490a88bd9a83bd8a9d0f69931e697adcae9aa002bc1c7ba7512fa2c3234
+MISC metadata.xml 696 RMD160 eefee5a91f449b16d3cbfdcbb453bf47e5a7b25b SHA1 5873b8e2863157effacdb823d69c63dd576c1105 SHA256 957d52534fbae4f869ed4443c46dc06a14f8474c0a294c7c878a5355b9e48e90
diff --git a/app-office/unoconv/metadata.xml b/app-office/unoconv/metadata.xml
index 46a44e5..5e8bbe6 100644
--- a/app-office/unoconv/metadata.xml
+++ b/app-office/unoconv/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>unoconv converts between any document format that OpenOffice understands. It uses OpenOffice's UNO bindings for non-interactive conversion of documents.
+
+Supported document formats include Open Document Format (.odt), MS Word (.doc), MS Office Open/MS OOXML (.xml), Portable Document Format (.pdf), HTML, XHTML, RTF, Docbook (.xml), and more.</longdescription>
+<use />
</pkgmetadata>
diff --git a/dev-games/cel/ChangeLog b/dev-games/cel/ChangeLog
index 6eff27d..5c6a6de 100644
--- a/dev-games/cel/ChangeLog
+++ b/dev-games/cel/ChangeLog
@@ -1,67 +1,13 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for dev-games/cel
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*cel-1.4.0 (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)
+ 27 Mar 2011; Sven Eden <sven.eden@gmx.de> +cel-1.4.0.ebuild : Initial
+ commit of the ebuild.
- DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
- an earlier ChangeLog entry.
+*cel-1.9_pre9999 (27 Mar 2011)
--- 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> +cel-1.9_pre9999.ebuild : Initial
+ commit of the ebuild.
diff --git a/dev-games/cel/Manifest b/dev-games/cel/Manifest
index d837b55..6968e33 100644
--- a/dev-games/cel/Manifest
+++ b/dev-games/cel/Manifest
@@ -1,5 +1,5 @@
DIST cel-src-1.4.0.tar.bz2 5114202 RMD160 d41f4fca69963d283a1bc52914b52b151c3f06cf SHA1 4ed93ebb70d3a2a116114e44884d2bab57597e07 SHA256 ee9eed9c7a5d660b2c2e1ef6048069ade19f6ce1c4e02b26c36bc3c286c76964
EBUILD cel-1.4.0.ebuild 1167 RMD160 226d9e93ad353a204205ab58e7743fb952ddcc38 SHA1 7ff1752c15fb241176291a66651f69c8ae7262a8 SHA256 2827e2348686fa334da6f7ae7ec6bb23ff28caeb6f6bea1020df838580200f4f
EBUILD cel-1.9_pre9999-r3.ebuild 1703 RMD160 c18300b81bb6d0004d0fd7efacc6c96336989db7 SHA1 464ef0efcefd368407be1825b51a5551718224e6 SHA256 fea429b9af983fed756666d1d3db45af435bb1a465b2e658b0c3844bc1628a08
-MISC cel-1.4.0.ebuild~ 1230 RMD160 49675996a4ca6246dc1dcb4092404e90b2075a1d SHA1 bdad13a35e099dd50516ac0279e90de3179ccfd8 SHA256 caa9deaecf7346c15630ca49a2ac624445c2d171f705a8b2023b944e8630dda7
-MISC cel-1.9_pre9999-r3.ebuild~ 1702 RMD160 4a8a6c19e33952afa66d7c67d96d19d949fb9912 SHA1 5ed9dc131b31ee45b53196fe1de8b017c21e638e SHA256 109617323d76d5ecc92d6e1a556da71fb86b6b1c51f981631b25456215434119
+MISC ChangeLog 371 RMD160 7cc14452b045a55c1663acc957964ca9e91cb0b1 SHA1 c21dbbbe06e00f13449c4d28300b5a8ef9047cce SHA256 08e2eb24f8978d2169a8dd00ccf82e5798185267b9b69936a327942aa89f10ad
+MISC metadata.xml 742 RMD160 ba57eb7e3665c99178c6f4aa87295f733078f1e7 SHA1 05b96b7763e8d31c7fdf288ff5d64cac1dbdb869 SHA256 8bba1c11f1a37559c759d853e6bed13ac5a288180366d18623bdcf19bd971ef2
diff --git a/dev-games/cel/metadata.xml b/dev-games/cel/metadata.xml
index 46a44e5..6ca9f5a 100644
--- a/dev-games/cel/metadata.xml
+++ b/dev-games/cel/metadata.xml
@@ -1,34 +1,14 @@
<?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>Entity system supporting higher-level functionality, such as runtime package environment (CELstart), generic event system, avatar and camera management, artificial intelligence (behavior trees, path finding, neural networks and genetic algorithms), vehicles, and more. </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='python'>Add Python bindings/flag>
+ <flag name='debug'>Build debug versions of the libraries</flag>
</use>
--->
</pkgmetadata>
diff --git a/dev-games/crystalspace/ChangeLog b/dev-games/crystalspace/ChangeLog
index 6eff27d..53db83d 100644
--- a/dev-games/crystalspace/ChangeLog
+++ b/dev-games/crystalspace/ChangeLog
@@ -1,67 +1,13 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for dev-games/crystalspace
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*crystalspace-1.4.0-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)
+ 27 Mar 2011; Sven Eden <sven.eden@gmx.de> +crystalspace-1.4.0-r2.ebuild :
+ Initial commit of the ebuild.
- DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
- an earlier ChangeLog entry.
+*crystalspace-1.9_pre9999-r5 (27 Mar 2011)
--- 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> +crystalspace-1.9_pre9999-r5.ebuild :
+ Initial commit of the ebuild.
diff --git a/dev-games/crystalspace/Manifest b/dev-games/crystalspace/Manifest
index 7c7a24e..173b7b2 100644
--- a/dev-games/crystalspace/Manifest
+++ b/dev-games/crystalspace/Manifest
@@ -2,6 +2,6 @@ AUX crystalspace-1.4.0-bullet.patch 501 RMD160 8a5c37029c5c1470d1c73b5e0b38df093
DIST crystalspace-src-1.4.0.tar.bz2 45670477 RMD160 af89e74a96bac7f55079a6cdad7fd938a38af602 SHA1 10f4dd50c654ad9292602a91189a0ee78a8fe353 SHA256 a8e1bfc9328470121bfbc6cf98f2c310a34f6998978065aa2f6df7e02a0101ba
EBUILD crystalspace-1.4.0-r2.ebuild 3499 RMD160 aa8e97669720b3b3fe53672d46ff2352116a402b SHA1 3666a937bcf83e8d3cba582f9a661b691f18a6f8 SHA256 4fb1ca5b6921bbf182adfb80336c21e4f83fdd6b7f16dd35f17c9effc856cbbc
EBUILD crystalspace-1.9_pre9999-r5.ebuild 4796 RMD160 c9f6316314984ba2423ec969854c52dcd6de8ea7 SHA1 6865c6dc97296bca5e4df77964ed3a157692175b SHA256 2a2eaf1e0aaaba22a988167899ae48c3c2af2f10e66e47a852082c97d2ddb327
+MISC ChangeLog 428 RMD160 92039400ceeabd58027944a0b6f112afdf0d7fe0 SHA1 aa7db67b96a08c773c26b302ec9296287c672e16 SHA256 02f7b0fdfd5255113cecaddd5b1ca7948c36775e16555fe6604c825be3d49fb1
MISC config.log 44199 RMD160 a66b802ebc68d69c0d5083b69dc8f6daaf97d9c5 SHA1 15d68c4344b765b8164453e88789aa4aecb7d8a6 SHA256 fe079661825d0742a1881a1e5fe5ee12d2ce2a4c933e1ecb619f40731bcc877c
-MISC crystalspace-1.4.0-r2.ebuild~ 3611 RMD160 a9b0784f6dff024ed8b9b50ef045b9397eabcf66 SHA1 49049f294d56b2af329794b5e8e29e8f0ef48697 SHA256 cf49332a3bc1ccebc4862a7f363df86ed42f0457a00325a0a94a15c41b4e330a
-MISC crystalspace-1.9_pre9999-r5.ebuild~ 5197 RMD160 98c760ea6535018ab5a6c12d3fc767307e5278bf SHA1 f8d82c8da298665cb14485bcb927098702173170 SHA256 6ea8fb9fd9c238ad26a16b71d749d54a4418fbdae138506e00d6717e5dfb4c0a
+MISC metadata.xml 899 RMD160 4376cd20210034fc71a7876d091b73b972492a81 SHA1 757b7836b38dd2eb8b0d12f7f542b78e023f790b SHA256 d3e85643b716c81ba35064f3fb40735d2a9434fa290bf1d8dea36d26b73fce3b
diff --git a/dev-games/crystalspace/metadata.xml b/dev-games/crystalspace/metadata.xml
index 46a44e5..f3295be 100644
--- a/dev-games/crystalspace/metadata.xml
+++ b/dev-games/crystalspace/metadata.xml
@@ -1,34 +1,16 @@
<?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>Crystal Space — A modular, configurable, and extensible rendering engine supporting OpenGL and advanced features such as shaders and lighting systems, physics, 3D sounds, animation blending, foliage, terrain, virtual file system, physical peripherals, and more.</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='python'>Add Python bindings/flag>
+ <flag name='optimized'>Build optimized versions of the libraries (default)</flag>
+ <flag name='debug'>Build debug versions of the libraries</flag>
+ <flag name='profile'>Build profiling versions of the libraries (slow)</flag>
</use>
--->
</pkgmetadata>
diff --git a/dev-games/gigi/ChangeLog b/dev-games/gigi/ChangeLog
index 6eff27d..e6169bf 100644
--- a/dev-games/gigi/ChangeLog
+++ b/dev-games/gigi/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for dev-games/gigi
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*gigi-9999-r4 (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> +gigi-9999-r4.ebuild :
+ Initial commit of the ebuild.
diff --git a/dev-games/gigi/Manifest b/dev-games/gigi/Manifest
index 135b524..cf60984 100644
--- a/dev-games/gigi/Manifest
+++ b/dev-games/gigi/Manifest
@@ -1,4 +1,4 @@
AUX unbundle-ltdl.patch 2512 RMD160 b8a50ac34f4d1fc735f651e52d7c55d944a427b9 SHA1 b5f18d9711032ac05b88712ac5a548a7463e47fe SHA256 17dfd37046ea8ada7c2f72ac38284ad44e71a8e6bcfe625d3d65b32934b69612
EBUILD gigi-9999-r4.ebuild 2497 RMD160 bd0647921b7ae216f3c5a328ffd866bf36538f5c SHA1 4f2013992f9f1ce29b6f04ada5c207b6cca9550d SHA256 c0aeede84dbda27947df435c7439ed9e5e5978aae8e86ea4f237e259958846c7
-MISC gigi-9999-r4.ebuild~ 2496 RMD160 6d57d206440c62a43f8d52fa643ac57a00b3f227 SHA1 ee875b71c355012dde9c8c90502c3c2e24dc0b25 SHA256 0607ded47f64e6202fbf4659c91827a12a54bfd5dffc7cb073816cd4a1579bd3
-MISC metadata.xml 415 RMD160 c158a0812b6f6dc760faface5ef3a8e94c444ccb SHA1 84f75e762f70fbb024a76813fea16fee4edc9e90 SHA256 bb2af8072de4f8fd6e81aad8a88d5e26bf274c4609009325a1adfe939a6199a8
+MISC ChangeLog 243 RMD160 99712a0d709320af61d2e9e6bae8da7ffb87a2dd SHA1 90621cabb1a5b2e9a7c831d87e3745d25762a955 SHA256 84f953d8d7ff921787706ba38efc203e142a97bcdb34d7e88768a35294f55707
+MISC metadata.xml 906 RMD160 9629337edec919d6296209ccf79fd7a6eebd01b4 SHA1 1f1a8f81b997fc6bf4879276c7e93e112d8d7dd0 SHA256 c191681c53ae611d3e0eac5b1b892963913f2e86529fe63c98ad66a89b7bfe7c
diff --git a/dev-games/gigi/metadata.xml b/dev-games/gigi/metadata.xml
index 0cccbc7..65fe564 100644
--- a/dev-games/gigi/metadata.xml
+++ b/dev-games/gigi/metadata.xml
@@ -1,11 +1,12 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
+<herd>no-herd</herd>
<maintainer>
- <email>krytzz@soylent.eu</email>
- <name>steffen stramm</name>
+ <email>sven.eden@gmx.de</email>
+ <description>The creator of this ebuild, but not the official maintainer</description>
</maintainer>
-<herd>games</herd>
+<longdescription>GiGi (aka GG) is a GUI library for OpenGL. It is platform-independent (it runs at least on Linux and Windows, and probably more), compiler-independent (it compiles under at GCC 3.4 or higher and MSVC++ 8.0 SP1 or higher, and probably more), and driver-independent. Reference drivers for SDL and Ogre are provided, and it is straightforward to write one for yourself should you decide to do so.</longdescription>
<use>
<flag name='devil'>Enable image loading via DevIL.</flag>
<flag name='ois'>Enable OIS support.</flag>
diff --git a/games-roguelike/tomenet/ChangeLog b/games-roguelike/tomenet/ChangeLog
index 6eff27d..d412416 100644
--- a/games-roguelike/tomenet/ChangeLog
+++ b/games-roguelike/tomenet/ChangeLog
@@ -1,67 +1,9 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for games-roguelike/tomenet
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*tomenet-100908 (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)
+ 27 Mar 2011; Sven Eden <sven.eden@gmx.de> +tomenet-100908.ebuild : Initial
+ commit of the ebuild.
- 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.
diff --git a/games-roguelike/tomenet/Manifest b/games-roguelike/tomenet/Manifest
index 6c37bac..8c4f633 100644
--- a/games-roguelike/tomenet/Manifest
+++ b/games-roguelike/tomenet/Manifest
@@ -1,3 +1,4 @@
DIST tomenet-cvs-snapshot-100908.tar.bz2 2330681 RMD160 07e7e2d6b31efde85c35a0fb52f58fa43865632c SHA1 7c82bdd0ca3ed45eea52b19dc3cbea147305e0a5 SHA256 7910820058fe9d7caf2b3722972212c174c42489e5873bb72ff62b478dac1008
EBUILD tomenet-100908.ebuild 1285 RMD160 2da39ef4d0013cbb42fc02d9b421b0d8fb95bafe SHA1 8c419101fa89c2fab54ecd26b136ea43d58278d4 SHA256 d950e3076b0b7aedba7118ce80728f46e88c0a475c5a900ff71ae768fba82a44
-MISC tomenet-100908.ebuild~ 1395 RMD160 7c4058aa2772bccfffab1474f349b7530522620d SHA1 f30093110002c798d31428b62ce54b57447c8150 SHA256 3685ef5bfb91de41bd6df1466f359b88d72b9db7a17963887f347119d69304da
+MISC ChangeLog 257 RMD160 05c5ef1d956005c5d1f3f7a98d52b80b83bc66d6 SHA1 2901cb7e8d68ba64acad5829c7e55245bb2a3c34 SHA256 fd7674788b68576feeef35d8a8cbb6529cd95d78e8dca190f2ca06ff3a1b0d29
+MISC metadata.xml 861 RMD160 84d66261eb52501829f19cfa704972a0fe665bc6 SHA1 aaaf932db7fb989c13190bb0dca9eea484188617 SHA256 8aa5881cdbf358e9ebc6a6dea7316291b67d321d310bfb67ea2052f678727749
diff --git a/games-roguelike/tomenet/metadata.xml b/games-roguelike/tomenet/metadata.xml
index 46a44e5..90473f2 100644
--- a/games-roguelike/tomenet/metadata.xml
+++ b/games-roguelike/tomenet/metadata.xml
@@ -1,34 +1,14 @@
<?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>TomeNET is a multiplayer fantasy dungeon exploration game based on the works of J.R.R. Tolkien. It is a game that emphasizes intricate, challenging, and varied gameplay over graphics. Hundreds of different monsters in randomly-generated, unpredictable dungeons will strive to slay you by various means, and you counter - if you survive - by developing the skills of your choice and wielding mighty artifacts.</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='X'>Enable libX11 display/flag>
+ <flag name='Xaw3d'>Enable Xaw3d display</flag>
</use>
--->
</pkgmetadata>
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>
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>
diff --git a/media-libs/jbig2enc/ChangeLog b/media-libs/jbig2enc/ChangeLog
index 6eff27d..428827d 100644
--- a/media-libs/jbig2enc/ChangeLog
+++ b/media-libs/jbig2enc/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for media-libs/jbig2enc
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*jbig2enc-0.26_pre9999 (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> +jbig2enc-0.26_pre9999.ebuild :
+ Initial commit of the ebuild.
diff --git a/media-libs/jbig2enc/Manifest b/media-libs/jbig2enc/Manifest
index 6ed6211..bcf6bc6 100644
--- a/media-libs/jbig2enc/Manifest
+++ b/media-libs/jbig2enc/Manifest
@@ -1,3 +1,4 @@
AUX local_to_gentoo_makefile.diff 1264 RMD160 d9cfd87e257394db8c561cbd8dc372da35bed89e SHA1 df07f5e9c2fd084e4d7fff95151fe0dea1868fc3 SHA256 49ee30fd8c2509dc1c5422640b909f926502f3ac416fd198011f4e6293af4597
EBUILD jbig2enc-0.26_pre9999.ebuild 929 RMD160 39eea874dfcc22943d00bfbc4ad1bb637293b44a SHA1 8a9c10ec86dfd4a285a08e49a736508576c2ea16 SHA256 20a9b80473607617c6a0616d05c1acf42f29529e1d1fbe299728f2a7af42fb7b
-MISC jbig2enc-0.26_pre9999.ebuild~ 927 RMD160 9c8a0db0e39ff6cb5d659307e535c4b202ef266e SHA1 f4ebe63b5197819a9fd0f6f411257ef2ebaa5cf7 SHA256 de0712e82fa88eaf174f184f11d84034bf5e2bd2c8296027f07a15fea9c19a8d
+MISC ChangeLog 266 RMD160 99a3749a309dc8e33f2c0b2a9b103db7c63690bf SHA1 20abea114b523cf3ce3e4795eac3d6c795264496 SHA256 d836c1f68cee23675d70dcd69219363003d44c7b59affd806723a53de03ab552
+MISC metadata.xml 363 RMD160 c640b825efd0eb007e5b64122dbf9166948cf4ae SHA1 2c06546dd209aa3c0ac88d688b644387da133a87 SHA256 0b51398a901ef4e1901e2d6f2acd7d63bc01e76039a52e85140e7d8b55d9e2c1
diff --git a/media-libs/jbig2enc/metadata.xml b/media-libs/jbig2enc/metadata.xml
index 46a44e5..eadd8f9 100644
--- a/media-libs/jbig2enc/metadata.xml
+++ b/media-libs/jbig2enc/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/media-libs/leptonica/ChangeLog b/media-libs/leptonica/ChangeLog
index 6eff27d..1fdfd8e 100644
--- a/media-libs/leptonica/ChangeLog
+++ b/media-libs/leptonica/ChangeLog
@@ -1,67 +1,8 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for media-libs/leptonica
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*leptonica-1.67 (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> +leptonica-1.67.ebuild : Initial
+ commit of the ebuild.
diff --git a/media-libs/leptonica/Manifest b/media-libs/leptonica/Manifest
index 13d755d..dd2d6f0 100644
--- a/media-libs/leptonica/Manifest
+++ b/media-libs/leptonica/Manifest
@@ -1,4 +1,5 @@
AUX leptonica-build-shared.diff 1123 RMD160 e4b621c406d143214d2d0c8cb4ff7fa6173ede25 SHA1 9dc0b648e4c6cea27eb4108652ce12e36360a759 SHA256 e382e206797fb179cf2fecb38a89f40257f2879e27bea614d460a0fc61dc76e7
DIST leptonlib-1.67.tar.gz 6618905 RMD160 0b0d9e9055400376239e74b9b13036857bc90ab4 SHA1 3240ae930784b79eb75058cf8cd0d02baa9627e8 SHA256 708ee1792835bc6bbf5ed254d439c42de87e44660c83e102491fa5a3f7f04227
EBUILD leptonica-1.67.ebuild 1196 RMD160 52110179a6b8347e168a2b48f3840d19a5b43e43 SHA1 4cd7055124275dc5f45fbe062936c5f7f8d7a638 SHA256 ac864c08184511d27ca9591669e744e191360a5654db1b0746750f5e62ccfe69
-MISC leptonica-1.67.ebuild~ 1287 RMD160 108442a37dff1d2c5602262a97c797797c0d4698 SHA1 66e03b96586e78e3287446f3cdd221fc6f9092a2 SHA256 fbecb49d6e0d1e7b944196ee5376736014aa7eaad1593c767a700b00b371318d
+MISC ChangeLog 253 RMD160 0d9ddb94cdde3d3ec461133427c01a83eb8183f2 SHA1 26a4424139e4cd2fda9cd665e23ab4395bdf49da SHA256 c344ad8a206da277a8e88b0dd543b8947dd95bf923ad2b5d532b3f21ff3fe205
+MISC metadata.xml 363 RMD160 c640b825efd0eb007e5b64122dbf9166948cf4ae SHA1 2c06546dd209aa3c0ac88d688b644387da133a87 SHA256 0b51398a901ef4e1901e2d6f2acd7d63bc01e76039a52e85140e7d8b55d9e2c1
diff --git a/media-libs/leptonica/metadata.xml b/media-libs/leptonica/metadata.xml
index 46a44e5..eadd8f9 100644
--- a/media-libs/leptonica/metadata.xml
+++ b/media-libs/leptonica/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/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>
diff --git a/sys-power/cpufreqd/ChangeLog b/sys-power/cpufreqd/ChangeLog
index 6eff27d..3f71097 100644
--- a/sys-power/cpufreqd/ChangeLog
+++ b/sys-power/cpufreqd/ChangeLog
@@ -1,67 +1,10 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for sys-power/cpufreqd
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*cpufreqd-2.4.2-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> +cpufreqd-2.4.2-r1.ebuild :
+ Initial commit of the ebuild. This ebuild does nothing but applying
+ an additional patch to compile cpufreqd against kernel sources
+ 2.6.36+. Once the patch is in the tree, this ebuild will go away.
diff --git a/sys-power/cpufreqd/Manifest b/sys-power/cpufreqd/Manifest
index 15adb83..7f66ed4 100644
--- a/sys-power/cpufreqd/Manifest
+++ b/sys-power/cpufreqd/Manifest
@@ -5,4 +5,5 @@ AUX nvclock0.8b-fpic.patch 641 RMD160 08f803b690e1ebf69859b48604bc746a1ee3c0fd S
DIST cpufreqd-2.4.2.tar.bz2 299946 RMD160 a6c762dd34f5a74387b37b64843dbf968bc3c28d SHA1 88ff75f3f3d457c49178f1e557ba5435651e1427 SHA256 3b7810a3d244d9b10c8c151fd6037e7d14c9889cdf5cdff1867bd978b9f7482a
DIST nvclock0.8b.tar.gz 353127 RMD160 66cac5993dc141d00efaa95d8f5ec38ed53854f6 SHA1 ff0a9fe81a8f3227338ffccae143310df1b18551 SHA256 a1fbdb82837c33869c0ebfcb95b6e11fc53b86919e8d1d17265d1af71eb04393
EBUILD cpufreqd-2.4.2-r1.ebuild 1947 RMD160 37e9ac95e3bbd3a690ef0a2a583728db003e1481 SHA1 f27ee9d0c0b8519802a4edd7d3ff413fe414c485 SHA256 76fc8072efb88b245b59de36866d15d55d057174059402078c936acc6ac2ae22
-MISC cpufreqd-2.4.2-r1.ebuild~ 2048 RMD160 b4050d0ef8f55a1999e7300981f7e2ebf51ae466 SHA1 581cbb4a8e6c8b35a10e3f929ae96f9ea9d636f0 SHA256 e9d68c452ffaf68d8d2577d3b045cf71b9cfcb14da08578109a353c841e6875d
+MISC ChangeLog 428 RMD160 c1ae44def95d4bacd72f7caf2e8061e842181721 SHA1 789af6016d4cfbfb942d6d0231b43aa15a8c1c61 SHA256 84baea4d1670eeb3e9cd83f74ff745d27c2febb57804b2dae59e32ea079b5a47
+MISC metadata.xml 423 RMD160 d843208101d0e0aef245a5d5219e23ba0c7a38a6 SHA1 a88afdeb4b95664870a648ee552b15c329b6a8a9 SHA256 acc4e407d32dcef3e0806c8fec555d9b5bc59cfc5d38f5e989dd5fea62723c93
diff --git a/sys-power/cpufreqd/metadata.xml b/sys-power/cpufreqd/metadata.xml
index 46a44e5..6fa1076 100644
--- a/sys-power/cpufreqd/metadata.xml
+++ b/sys-power/cpufreqd/metadata.xml
@@ -1,34 +1,12 @@
<?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> -->
-</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>
--->
+ <herd>mobile</herd>
+ <use>
+ <flag name='nforce2'>Enable support for nforce2 voltage settings
+ plug-in</flag>
+ <flag name='nvidia'>Enable nvidia overclocking
+ (<pkg>media-video/nvclock</pkg>) plug-in</flag>
+ <flag name='pmu'>Enable Power Management Unit plug-in</flag>
+ </use>
</pkgmetadata>
diff --git a/www-apps/dotproject/ChangeLog b/www-apps/dotproject/ChangeLog
index 6eff27d..4bca894 100644
--- a/www-apps/dotproject/ChangeLog
+++ b/www-apps/dotproject/ChangeLog
@@ -1,67 +1,9 @@
-# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# ChangeLog for www-apps/dotproject
# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+*dotproject-2.1.5-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> +dotproject-2.1.5-r1.ebuild :
+ Initial commit of the ebuild. Simple version bump until the tree is
+ updated.
diff --git a/www-apps/dotproject/Manifest b/www-apps/dotproject/Manifest
index 95fcba1..4a49d37 100644
--- a/www-apps/dotproject/Manifest
+++ b/www-apps/dotproject/Manifest
@@ -1,4 +1,5 @@
AUX install-en.txt 793 RMD160 52b90aafed335845122e2117ae8c3fb510c1693d SHA1 2590df3221c75e80c967880069325edb5a038c6d SHA256 3745e3a4d5b9a642c9f409a8c09dc072787b687531f9adcfe31ea317bd3f7889
DIST dotproject-2.1.5.tar.gz 4524714 RMD160 d50f3b0ffd5fb390385b2c88420e660549696ca6 SHA1 89f80792bcf7344cb89142db614c7b34f8c67463 SHA256 86beef3a1280c3c2eccde6abe8ea0570e348fdecf756b581382fa8ad9aa331bf
EBUILD dotproject-2.1.5-r1.ebuild 1316 RMD160 f92be242c7bcdc7ef8fa502cfe6d34e055e096f7 SHA1 25217e364d181c0e883bdfecc2b5a37c5152063a SHA256 9dcf2a302a52f03d7310b3f0599086703c315bed3ac6a922b9696f4ce4026390
-MISC dotproject-2.1.5-r1.ebuild~ 1339 RMD160 fcf9020a1836f9a755d9c7d6a9b5635b619e4d68 SHA1 c1e0aa7f56b18998fb73601ee138b7aa8f50aa3a SHA256 514c4ecc4faf8fdba03a73220fb0f8dbac6ae0294b1c834a14f4e3253b63c3e2
+MISC ChangeLog 311 RMD160 8df61739111a8ed0fbb364852dd26943407ce572 SHA1 2f27231fd326a7f587a973c3d46669d848dae07f SHA256 1870dbb73c966bf09e61f0d3c243500d9789c148975e9f902eb908adb3e8aa97
+MISC metadata.xml 162 RMD160 0b015f5ff17c4d8e7aee826d48b326cc19b1fed4 SHA1 671b30dafbea01228c8bb606af451a0795922840 SHA256 84ff2fc6c9a4af1b9dbe32aa81ab84c2958bc1bd65a9977686df2dcab6e420d0
diff --git a/www-apps/dotproject/metadata.xml b/www-apps/dotproject/metadata.xml
index 46a44e5..6632069 100644
--- a/www-apps/dotproject/metadata.xml
+++ b/www-apps/dotproject/metadata.xml
@@ -1,34 +1,5 @@
<?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> -->
-</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>
--->
+ <herd>web-apps</herd>
</pkgmetadata>