public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: How to speed up maintenance and other Gentoo work?
Date: Fri, 6 Mar 2009 19:44:52 -0600	[thread overview]
Message-ID: <20090306194452.6b5bf4e5@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: 1236132096.2522.4.camel@localhost

[-- Attachment #1: Type: text/plain, Size: 1723 bytes --]

On Wed, 04 Mar 2009 04:01:36 +0200
Mart Raudsepp <leio@gentoo.org> wrote:

> I'm collecting ideas from the wider development and contributing
> community on how to help maintainers and contributors get work done
> quicker, or rephrased - how to get more done in the limited time we
> have.
> 
> This basically means ideas for tools, scripts, or functionality in
> some hypothetical centralized maintainer helper website or GUI/CLI
> program that would help save time in taking care of some of the
> gruntwork that gets done by maintainers right now manually or by
> scripts that don't get shared and re-used and generalized as much as
> they could.
> 
> Then afterwards I can sort through the suggestions/ideas, try to make
> a summary and arrange some of them to actually happen.

One tool I used a lot before metadata.xml USE flags sprung up
everywhere was metagen (in the tree under apps-portage), written by
pythonhead.  For anyone who hasn't used it, it's a commandline util
written in python (surprise!) for generating metadata.xml.  You can
give it a herd, maintainer name/email, maintainer description, package
description, etc., and it will hock out a xml loogie for you.  I've
been meaning to update it for USE flags (and whatever else we're
stuffing into xml these days) as a learn-python project, but like all
my learn-* projects it's never gotten anywhere.  Maybe someone with the
requisite skills and boredom level might be interested in poking at it.


-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-03-07  1:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04  2:01 [gentoo-dev] How to speed up maintenance and other Gentoo work? Mart Raudsepp
2009-03-04  2:24 ` Mike Frysinger
2009-03-04  5:37   ` Donnie Berkholz
2009-03-04  2:26 ` Peter Alfredsen
2009-03-04  2:51   ` Olivier Crête
2009-03-04  4:54     ` Josh Saddler
2009-03-04  5:36   ` Donnie Berkholz
2009-03-04 12:50 ` [gentoo-dev] " Nicolas Sebrecht
2009-03-07  7:22   ` Caleb Cushing
2009-03-07 11:21     ` Nicolas Sebrecht
2009-03-07 19:27     ` Alec Warner
2009-03-08  0:57       ` Caleb Cushing
2009-03-08  2:29         ` Robin H. Johnson
2009-03-08 14:10           ` Nicolas Sebrecht
2009-03-06 19:02 ` [gentoo-dev] " Petteri Räty
2009-03-07  1:44 ` Ryan Hill [this message]
2009-03-07  3:08   ` [gentoo-dev] " Duncan
2009-03-13  8:24 ` [gentoo-dev] " Thilo Bangert
2009-03-13 12:44   ` Grant Goodyear

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=20090306194452.6b5bf4e5@halo.dirtyepic.sk.ca \
    --to=dirtyepic@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