From: "Brian Dolbec" <dolsen@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoolkit:gentoolkit-dev commit in: /
Date: Wed, 22 Mar 2017 11:00:19 +0000 (UTC) [thread overview]
Message-ID: <1490180159.0b370f78fcb87c440d5b71908f27417ea3faf8a2.dolsen@gentoo> (raw)
commit: 0b370f78fcb87c440d5b71908f27417ea3faf8a2
Author: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
AuthorDate: Wed Mar 22 10:55:59 2017 +0000
Commit: Brian Dolbec <dolsen <AT> gentoo <DOT> org>
CommitDate: Wed Mar 22 10:55:59 2017 +0000
URL: https://gitweb.gentoo.org/proj/gentoolkit.git/commit/?id=0b370f78
Remove no longer needed readme and todo files in prep for gentoolkit merge
NEWS | 0
README | 36 ------------------------------------
README.Developer | 49 -------------------------------------------------
TODO | 6 ------
4 files changed, 91 deletions(-)
diff --git a/NEWS b/NEWS
deleted file mode 100644
index e69de29..0000000
diff --git a/README b/README
deleted file mode 100644
index bbc42f0..0000000
--- a/README
+++ /dev/null
@@ -1,36 +0,0 @@
-Package: gentoolkit-dev
-Authors: Aron Griffis <agriffis@gentoo.org>
- Brandon Low <lostlogic@gentoo.org>
- Ian Leitch <port001@gentoo.org>
- Karl Trygve Kalleberg <karltk@gentoo.org>
- Marius Mauch <genone@gentoo.org>
- Paul Varner <fuzzyray@gentoo.org>
- Christian Ruppert <idl0r@gentoo.org>
- See src/<tool>/AUTHORS for tool-specific authors
-
-MOTIVATION
-
-The gentoolkit and gentoolkit-dev packages contain a collection of useful
-administration scripts particular to the Gentoo Linux distribution. It contains
-rough drafts and implementations of features that may in time make it into
-Portage, or into full-fledged tools in their own right.
-
-The gentoolkit-dev package is intended primarily for Gentoo developers.
-
-CONTENTS
-
-gentoolkit-dev
-==============
-ebump - Ebuild revision bumper
-echangelog - update portage ChangeLogs
-ego -
-ekeyword - modify package KEYWORDS
-eviewcvs - generate viewcvs URLs
-imlate - Displays candidates for keywords for an architecture based upon a target architecture
-
-IMPROVEMENTS
-
-Any suggestions for improvements should be sent to tools-portage@gentoo.org, or
-added as a bug assigned to us.
-
-We only accept new contributions if they are written in bash or python.
diff --git a/README.Developer b/README.Developer
deleted file mode 100644
index d8d37b6..0000000
--- a/README.Developer
+++ /dev/null
@@ -1,49 +0,0 @@
-
-OVERVIEW
-
-The SVN module 'gentoolkit' contains all the scripts and stuff for both the
-gentoolkit and the gentoolkit-dev package. The gentoolkit-dev package is
-an optional add-on, that is only intented for the Gentoo developers.
-
-STYLE POLICY
-
-If you're touching any of the python scripts please don't change the indentation
-style (if it's using tabs, you should use tabs too). Especially don't mix
-spaces and tabs as that makes the code completely unreadable.
-Tabs should be default for new scripts.
-
-Each script must provide a manpage.
-
-MAKING A RELEASE
-
-Releases should only be made by members of the tools-portage team. See
-http://www.gentoo.org/proj/en/metastructure/herds/herds.xml?select=tools-portage
-for who to contact on IRC, or shuffle over a bug report to us, or send
-us a mail at tools-portage@gentoo.org if you need an immediate release.
-
-The release manager (big words;) will then do
-
-1) make VERSION=major.minor.patch RELEASE_TAG=<optional> dist
-2) copy release/gentoolkit-dev-${VERSION}-${RELEASE_TAG}.tar.gz to
- dev.gentoo.org:/space/distfiles-local/
-3) make a new ebuild, app-portage/gentoolkit-dev/gentoolkit-dev-${VERSION}.ebuild
- with a SRC_URI that points to
- mirror://gentoo/gentoolkit-dev-${VERSION}-${RELEASE_TAG}.tar.gz
- (just use one of the previous ebuilds)
-
-Important!
-1) _ALWAYS_ make sure you don't "overwrite" a previous release. Your
- new VERSION must be newer than any previous released version. If you
- mess up a release, don't overwrite with the same release number, iterate
- the patch version and try again (and again, and again until you get
- it right;)
-
-
-Currently, the following people have "release access":
-
- - zmedico@gentoo.org
- - fuzzyray@gentoo.org
- - idl0r@gentoo.org
-
-If you want a new release, ping either one of us. If you want to get
-"release access", talk to fuzzyray@gentoo.org
diff --git a/TODO b/TODO
deleted file mode 100644
index fee248d..0000000
--- a/TODO
+++ /dev/null
@@ -1,6 +0,0 @@
-- rewrite ekeyword and echangelog to use gentoolkit
-- look through forums.gentoo.org for additional scripts
-- write a Gentoolkit Guide
-
-- imlate
- Compare one arch with all others to see possible candidates for several architectures
next reply other threads:[~2017-03-22 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 11:00 Brian Dolbec [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-23 1:40 [gentoo-commits] proj/gentoolkit:gentoolkit-dev commit in: / Mike Frysinger
2017-03-22 11:00 Brian Dolbec
2017-03-22 11:00 Brian Dolbec
2017-03-22 11:00 Brian Dolbec
2017-03-22 11:00 Brian Dolbec
2017-03-22 11:00 Brian Dolbec
2017-03-22 11:00 Brian Dolbec
2014-11-15 18:37 Christian Ruppert
2013-05-11 19:28 Christian Ruppert
2013-05-10 17:24 Christian Ruppert
2013-05-10 15:26 Christian Ruppert
2012-04-23 3:02 Christian Ruppert
2011-03-23 16:30 Christian Ruppert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490180159.0b370f78fcb87c440d5b71908f27417ea3faf8a2.dolsen@gentoo \
--to=dolsen@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox