From 7bbd8ca9915a04c51f05b5ffef318c5033e2ecb0 Mon Sep 17 00:00:00 2001 From: Domen Kožar Date: Sun, 22 Aug 2010 14:36:11 +0200 Subject: fix gpypi2-9999 --- dev-python/g-pypi2/ChangeLog | 77 ------------------------------- dev-python/g-pypi2/g-pypi2-9999.ebuild | 34 -------------- dev-python/g-pypi2/metadata.xml | 8 ---- dev-python/gpypi2/ChangeLog | 83 ++++++++++++++++++++++++++++++++++ dev-python/gpypi2/gpypi2-9999.ebuild | 35 ++++++++++++++ dev-python/gpypi2/metadata.xml | 8 ++++ 6 files changed, 126 insertions(+), 119 deletions(-) delete mode 100644 dev-python/g-pypi2/ChangeLog delete mode 100644 dev-python/g-pypi2/g-pypi2-9999.ebuild delete mode 100644 dev-python/g-pypi2/metadata.xml create mode 100644 dev-python/gpypi2/ChangeLog create mode 100644 dev-python/gpypi2/gpypi2-9999.ebuild create mode 100644 dev-python/gpypi2/metadata.xml diff --git a/dev-python/g-pypi2/ChangeLog b/dev-python/g-pypi2/ChangeLog deleted file mode 100644 index 992d5c9..0000000 --- a/dev-python/g-pypi2/ChangeLog +++ /dev/null @@ -1,77 +0,0 @@ -# ChangeLog for dev-python/g-pypi2 -# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2 -# $Header: $ - - 19 Jul 2010; Domen Kožar g-pypi2-9999.ebuild: - Fixed mistakes in ebuild, added gentoolkit dependency and distutils - inherit - -*g-pypi2-9999 (07 Jul 2010) - - 07 Jul 2010; Domen Kožar +g-pypi2-9999.ebuild, - +metadata.xml: - Add inital ebuild - -*-- (DD MMM YYYY) - - DD MMM YYYY; YOUR_NAME changed_file1, changed_file2 : - Initial import. Ebuild submitted by submitter_name . - 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 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 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-python/g-pypi2/g-pypi2-9999.ebuild b/dev-python/g-pypi2/g-pypi2-9999.ebuild deleted file mode 100644 index f1c17e9..0000000 --- a/dev-python/g-pypi2/g-pypi2-9999.ebuild +++ /dev/null @@ -1,34 +0,0 @@ -# Copyright 1999-2010 Gentoo Foundation -# Distributed under the terms of the GNU General Public License v2 -# $Header: $ - -EAPI="3" - -inherit eutils distutils - -DESCRIPTION="creates ebuilds for Gentoo Linux from Python Package Index" -HOMEPAGE="http://docs.fubar.si/gpypi2/" -SRC_URI="http://bitbucket.org/iElectric/${PN}/get/tip.tar.gz" -LICENSE="BSD-2" -SLOT="0" -KEYWORDS="~amd64 ~x86" - -IUSE="test doc" - -DEPEND="dev-python/unittest2 - dev-python/jinja2 - dev-python/yolk - dev-python/pygments - dev-python/argparse - app-portage/gentoolkit - test? dev-python/nose - test? dev-python/mock - test? dev-python/ScriptTest - doc? dev-python/Sphinx" - -# Run-time dependencies. Must be defined to whatever this depends on to run. -# The below is valid if the same run-time depends are required to compile. -RDEPEND="${DEPEND}" - -DOCS="README LICENSE" -PTHON_MODNAME="gpypi2" diff --git a/dev-python/g-pypi2/metadata.xml b/dev-python/g-pypi2/metadata.xml deleted file mode 100644 index d2c27ad..0000000 --- a/dev-python/g-pypi2/metadata.xml +++ /dev/null @@ -1,8 +0,0 @@ - - - -no-herd - - domen@dev.si - - diff --git a/dev-python/gpypi2/ChangeLog b/dev-python/gpypi2/ChangeLog new file mode 100644 index 0000000..cd0aa1b --- /dev/null +++ b/dev-python/gpypi2/ChangeLog @@ -0,0 +1,83 @@ +# ChangeLog for dev-python/gpypi2 +# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2 +# $Header: $ + +*gpypi2-9999 (22 Aug 2010) + + 22 Aug 2010; Domen Kožar +gpypi2-9999.ebuild, + +metadata.xml: + Renamed package and fixed dependencies + + 19 Jul 2010; Domen Kožar g-pypi2-9999.ebuild: + Fixed mistakes in ebuild, added gentoolkit dependency and distutils + inherit + +*g-pypi2-9999 (07 Jul 2010) + + 07 Jul 2010; Domen Kožar +g-pypi2-9999.ebuild, + +metadata.xml: + Add inital ebuild + +*-- (DD MMM YYYY) + + DD MMM YYYY; YOUR_NAME changed_file1, changed_file2 : + Initial import. Ebuild submitted by submitter_name . + 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 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 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-python/gpypi2/gpypi2-9999.ebuild b/dev-python/gpypi2/gpypi2-9999.ebuild new file mode 100644 index 0000000..2b8faa5 --- /dev/null +++ b/dev-python/gpypi2/gpypi2-9999.ebuild @@ -0,0 +1,35 @@ +# Copyright 1999-2010 Gentoo Foundation +# Distributed under the terms of the GNU General Public License v2 +# $Header: $ + +EAPI="3" + +inherit eutils distutils + +DESCRIPTION="creates ebuilds for Gentoo Linux from Python Package Index" +HOMEPAGE="http://docs.fubar.si/gpypi2/" +SRC_URI="http://bitbucket.org/iElectric/g-pypi2/get/tip.zip" +LICENSE="BSD-2" +SLOT="0" +KEYWORDS="~amd64 ~x86" + +IUSE="test doc" + +DEPEND="dev-python/unittest2 + dev-python/jinja + dev-python/yolk + dev-python/pygments + dev-python/argparse + app-portage/gentoolkit + app-portage/gentoolkit-dev + >=app-portage/metagen-0.5.2 + test? ( dev-python/nose ) + test? ( dev-python/mock ) + test? ( dev-python/scripttest ) + doc? ( dev-python/sphinx )" + +# Run-time dependencies. Must be defined to whatever this depends on to run. +# The below is valid if the same run-time depends are required to compile. +RDEPEND="${DEPEND}" + +S="${WORKDIR}/g-pypi2/" diff --git a/dev-python/gpypi2/metadata.xml b/dev-python/gpypi2/metadata.xml new file mode 100644 index 0000000..d2c27ad --- /dev/null +++ b/dev-python/gpypi2/metadata.xml @@ -0,0 +1,8 @@ + + + +no-herd + + domen@dev.si + + -- cgit v1.2.3-65-gdbad