public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: RFC: Last rites for $package ...
Date: Tue, 10 Oct 2006 13:50:10 +0100	[thread overview]
Message-ID: <egg4kf$di8$1@sea.gmane.org> (raw)
In-Reply-To: 200609301210.04828.bangert@gentoo.org

>> Or you haven't talked to me or Beandog at all; since he has been
>> working on this a while (now with upgraded tools!).
> 
> what i'd like to see is a system, to which one would give a package name,
> which then handles the removal (almost) automatically.
> 
> that way devs would have an easier time actually removing some cruft and
> you guys would be freed from typing the same stuff over and over.
> this system could be responsible for sending the out last rites mails,
> masking the packages in package.mask etc... enrico would get his database
> for free, both listing those that are pending removal as well as a
> history of removals including the reason plus a pointer to the
> corresponding bug...
> 
This sounds like an excellent idea. Do the `upgraded tools' already automate
this process?

After all, that's what computers are good at- automating workflow.

> don't know if that is what you are aiming at, but currently the process of
> removing a package is a true chore and i admire your dedication to it. (a
> big THANKS btw)
> 
++


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-10-10 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 20:28 [gentoo-dev] RFC: Last rites for $package Enrico Weigelt
2006-09-28 20:48 ` Joshua Jackson
2006-09-28 20:54 ` Mike Kelly
2006-09-28 20:57 ` Steve Dibb
2006-09-28 21:01 ` Alec Warner
2006-09-30 10:10   ` Thilo Bangert
2006-10-10 12:50     ` Steve Long [this message]
2006-10-10 13:03       ` [gentoo-dev] " Alec Warner
2006-10-10 15:23         ` [gentoo-dev] " Steve Long

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='egg4kf$di8$1@sea.gmane.org' \
    --to=slong@rathaus.eclipse.co.uk \
    --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