diff options
32 files changed, 1409 insertions, 3 deletions
diff --git a/app-emulation/puae/ChangeLog b/app-emulation/puae/ChangeLog new file mode 100644 index 0000000..02732ed --- /dev/null +++ b/app-emulation/puae/ChangeLog @@ -0,0 +1,17 @@ +# ChangeLog for app-emulation/puae +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*puae-2.3.2_pre9999 (28 Mar 2011) + + 28 Mar 2011; Sven Eden <seden@gmx.de> +puae-2.3.2_pre9999.ebuild : Upstream + has changed the version number. But as it is still a live version, the + pre9999 suffix will stay + + 28 Mar 2011; Sven Eden <seden@gmx.de> -puae-2.3.1_pre9999.ebuild : Remove + old ebuild, git pull is unversioned. + +*puae-2.3.1_pre9999 (27 Mar 2011) + + 27 Mar 2011; Sven Eden <seden@gmx.de> +puae-2.3.1_pre9999.ebuild : Initial + release via seden overlay. diff --git a/app-emulation/puae/metadata.xml b/app-emulation/puae/metadata.xml index 3bb16e5..b805b0c 100644 --- a/app-emulation/puae/metadata.xml +++ b/app-emulation/puae/metadata.xml @@ -6,7 +6,15 @@ <email>sven.eden@gmx.de</email> <description>The creator of this ebuild, but not the official maintainer</description> </maintainer> -<!-- <longdescription></longdescription> --> +<longdescription>PUAE tries to continue where E-UAE left off.. +PUAE versioning is based on the merged WinUAE version.. + +All is done by: + Mustafa 'GnoStiC' TUFAN (mustafa.tufan@gmail.com) + +with fixes from: + Steven 'xaind' Saunders (MacOSX) + 'wuffe' (FreeBSD)</longdescription> <use> <flag name='profiling'>Build a profiling (SLOW!) version</flag> <!-- currently broken, won't compile/link <flag name='a2065'>Enable A2065 Ethernet emulation</flag> --> diff --git a/app-emulation/puae/puae-2.3.1_pre9999.ebuild b/app-emulation/puae/puae-2.3.2_pre9999.ebuild index 6b3789e..6b3789e 100644 --- a/app-emulation/puae/puae-2.3.1_pre9999.ebuild +++ b/app-emulation/puae/puae-2.3.2_pre9999.ebuild diff --git a/app-emulation/winetricks/ChangeLog b/app-emulation/winetricks/ChangeLog new file mode 100644 index 0000000..fa8dd3d --- /dev/null +++ b/app-emulation/winetricks/ChangeLog @@ -0,0 +1,17 @@ +# ChangeLog for app-emulation/winetricks +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*winetricks-9999-r1 (28 Mar 2011) + + 28 Mar 2011; Sven Eden <sven.eden@gmx.de> +winetricks-9999-r1.ebuild : New + ebuild with corrected USE flags, as it should be "gnome", not "gtk" to pull + a dependency to something in gnome-extra in. + + 28 Mar 2011; Sven Eden <sven.eden@gmx.de> -winetricks-9999.ebuild : Removed + old ebuild + +*winetricks-9999 (27 Mar 2011) + + 27 Mar 2011; Sven Eden <sven.eden@gmx.de> +winetricks-9999.ebuild : Initial + release via seden overlay. diff --git a/app-emulation/winetricks/metadata.xml b/app-emulation/winetricks/metadata.xml new file mode 100644 index 0000000..15da9c8 --- /dev/null +++ b/app-emulation/winetricks/metadata.xml @@ -0,0 +1,18 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> +<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>Winetricks is an easy way to work around problems in Wine. + +It has a menu of supported games/apps for which it can do all the workarounds automatically. It also lets you install missing DLLs or tweak various Wine settings individually. + +It can be used via gui or commandline, whichever you prefer; the commandline mode is particularly useful as a building block in fancier wine frontends and in automated regression testing. </longdescription> +<use> + <flag name='gnome'>Use gnome-extra/zenity to display the GUI</flag> + <flag name='kde'>Use kde-base/kdialog to display the GUI</flag> +</use> +</pkgmetadata> diff --git a/app-emulation/winetricks/winetricks-9999.ebuild b/app-emulation/winetricks/winetricks-9999-r1.ebuild index 5a29b5e..9aca8b0 100644 --- a/app-emulation/winetricks/winetricks-9999.ebuild +++ b/app-emulation/winetricks/winetricks-9999-r1.ebuild @@ -13,14 +13,14 @@ ESVN_PROJECT="${PN}" LICENSE="LGPL-2.1" KEYWORDS="~amd64 ~x86" -IUSE="gtk kde" +IUSE="gnome kde" SLOT="0" DEPEND="" RDEPEND=" app-emulation/wine - gtk? ( gnome-extra/zenity ) + gnome? ( gnome-extra/zenity ) kde? ( kde-base/kdialog ) " diff --git a/app-office/unoconv/ChangeLog b/app-office/unoconv/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/app-office/unoconv/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/app-office/unoconv/metadata.xml b/app-office/unoconv/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/app-office/unoconv/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/dev-games/cel/ChangeLog b/dev-games/cel/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/dev-games/cel/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/dev-games/cel/metadata.xml b/dev-games/cel/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/dev-games/cel/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/dev-games/crystalspace/ChangeLog b/dev-games/crystalspace/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/dev-games/crystalspace/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/dev-games/crystalspace/metadata.xml b/dev-games/crystalspace/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/dev-games/crystalspace/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/dev-games/gigi/ChangeLog b/dev-games/gigi/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/dev-games/gigi/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/games-roguelike/tomenet/ChangeLog b/games-roguelike/tomenet/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/games-roguelike/tomenet/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/games-roguelike/tomenet/metadata.xml b/games-roguelike/tomenet/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/games-roguelike/tomenet/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/games-strategy/freeorion/ChangeLog b/games-strategy/freeorion/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/games-strategy/freeorion/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/games-strategy/glfrontier/ChangeLog b/games-strategy/glfrontier/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/games-strategy/glfrontier/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/games-strategy/glfrontier/metadata.xml b/games-strategy/glfrontier/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/games-strategy/glfrontier/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/games-strategy/seven-kingdoms/ChangeLog b/games-strategy/seven-kingdoms/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/games-strategy/seven-kingdoms/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/games-strategy/seven-kingdoms/metadata.xml b/games-strategy/seven-kingdoms/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/games-strategy/seven-kingdoms/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/media-gfx/nvidia-cg-toolkit/ChangeLog b/media-gfx/nvidia-cg-toolkit/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/media-gfx/nvidia-cg-toolkit/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/media-gfx/nvidia-cg-toolkit/metadata.xml b/media-gfx/nvidia-cg-toolkit/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/media-gfx/nvidia-cg-toolkit/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/media-libs/jbig2enc/ChangeLog b/media-libs/jbig2enc/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/media-libs/jbig2enc/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/media-libs/jbig2enc/metadata.xml b/media-libs/jbig2enc/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/media-libs/jbig2enc/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/media-libs/leptonica/ChangeLog b/media-libs/leptonica/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/media-libs/leptonica/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/media-libs/leptonica/metadata.xml b/media-libs/leptonica/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/media-libs/leptonica/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/net-mail/davmail/ChangeLog b/net-mail/davmail/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/net-mail/davmail/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/net-mail/davmail/metadata.xml b/net-mail/davmail/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/net-mail/davmail/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/sys-power/cpufreqd/ChangeLog b/sys-power/cpufreqd/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/sys-power/cpufreqd/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/sys-power/cpufreqd/metadata.xml b/sys-power/cpufreqd/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/sys-power/cpufreqd/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> diff --git a/www-apps/dotproject/ChangeLog b/www-apps/dotproject/ChangeLog new file mode 100644 index 0000000..6eff27d --- /dev/null +++ b/www-apps/dotproject/ChangeLog @@ -0,0 +1,67 @@ +# ChangeLog for <CATEGORY>/<PACKAGE_NAME> +# Copyright 1999-2011 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) + + 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. diff --git a/www-apps/dotproject/metadata.xml b/www-apps/dotproject/metadata.xml new file mode 100644 index 0000000..46a44e5 --- /dev/null +++ b/www-apps/dotproject/metadata.xml @@ -0,0 +1,34 @@ +<?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> +--> +</pkgmetadata> |