From: Karl Trygve Kalleberg <karltk@gentoo.org>
To: Ian Leitch <port001@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] app-portage/gentoolkit-0.2.0_pre1 almost available for testing
Date: Wed, 7 Jan 2004 20:19:17 +0100 [thread overview]
Message-ID: <20040107191917.GG1994@boblycat.org> (raw)
In-Reply-To: <1073502300.14215.4.camel@Interimo.boxen>
On Wed, Jan 07, 2004 at 07:05:00PM +0000, Ian Leitch wrote:
>
> Hi Karl,
>
> When is the user/dev tools split going to happen? I currently have one
> package 'epkgmove'[1] ready for release plus another two called esign
> and eorphan to follow shortly.
>
> [1] http://dev.gentoo.org/~port001/DevTools/epkgmove/
I'm happy to inform you that it's already happened. I just haven't added
the ebuild for it yet.
If you make one bug issues out of each of your scripts and assign them
to me, I'll take add them to app-portage/gentoolkit-dev-0.2.0_pre1 as I
release it either later tonight or tomorrow.
Just some general info: Getting tools into gentoolkit-dev should be
fairly straightforward if you're willing to do the required maintenance.
As for gentoolkit, which is targeted at our users, we'll be a bit more
strict, and will only add new tools that we (the tools-portage herd) are
willing to maintain.
Experience tells us that most of the tools that have gone into
gentoolkit over the years were not maintained by the original
contributor, despite vehement insistence and oaths of proper
maintainenance from the original contributor(s) at inclusion time.
Kind regards,
Karl T
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-01-07 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 14:19 [gentoo-dev] app-portage/gentoolkit-0.2.0_pre1 almost available for testing Karl Trygve Kalleberg
2004-01-07 18:31 ` Paul Varner
2004-01-07 19:22 ` Karl Trygve Kalleberg
2004-01-07 19:05 ` Ian Leitch
2004-01-07 19:19 ` Karl Trygve Kalleberg [this message]
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=20040107191917.GG1994@boblycat.org \
--to=karltk@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=port001@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