From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Unused ebuild built_with_use cleanup
Date: Tue, 27 Oct 2009 09:46:11 -0400 [thread overview]
Message-ID: <200910270946.12243.vapier@gentoo.org> (raw)
In-Reply-To: <4AE6F11C.9010804@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1432 bytes --]
On Tuesday 27 October 2009 09:09:48 Petteri Räty wrote:
> Mike Frysinger wrote:
> > On Tuesday 27 October 2009 02:07:02 Ryan Hill wrote:
> >> On Sun, 25 Oct 2009 11:48:39 +0200 Petteri Räty wrote:
> >>> James Cloos wrote:
> >>>> When you first psoted this list I noticed some (or several?) live
> >>>> ebuilds. Git-9999 is the one I remember.
> >>>>
> >>>> Those should not get nuked during global cleanups, as they are likely
> >>>> to be in active use notwithstanding their keywording or masking.
> >>>
> >>> Their maintainers should be active and switch their ebuilds to EAPI 2.
> >>> If they don't have an active maintainer, then do we want to keep live
> >>> ebuilds for them around?
> >>
> >> Your stated goal was to remove unused ebuilds, which live ebuilds are
> >> not, regardless of the status of the maintainer. And I'm pretty sure
> >> git has an active maintainer. :P
> >
> > indeed. you really should file bugs for these instead of deleting
> > ebuilds on people who missed a thread on gentoo-dev.
>
> All developers are required to follow gentoo-dev-announce. If they don't
> follow that, it can't be expected for them to follow bugzilla either.
that's a poor excuse. file bugs instead of tromping on other people's
packages since you clearly have a list of ebuilds you shouldnt be removing and
you dont intend to fix. i doubt Ryan's example of git-9999 is the only one.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-10-27 13:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 13:32 [gentoo-dev] Unused ebuild built_with_use cleanup Petteri Räty
2009-10-07 11:21 ` Marijn Schouten (hkBst)
2009-10-08 21:29 ` Petteri Räty
2009-10-07 11:54 ` Stelian Ionescu
2009-10-08 21:34 ` Petteri Räty
2009-10-08 22:03 ` Jeremy Olexa
2009-10-08 22:22 ` Petteri Räty
2009-10-09 0:17 ` Patrick Lauer
2009-10-09 13:38 ` Petteri Räty
2009-10-08 22:25 ` Tomáš Chvátal
2009-10-09 13:41 ` Petteri Räty
2009-10-24 12:32 ` [gentoo-dev] Re: [gentoo-dev-announce] " Petteri Räty
2009-10-24 20:29 ` James Cloos
2009-10-25 9:48 ` Petteri Räty
2009-10-26 23:21 ` James Cloos
2009-10-27 13:12 ` Petteri Räty
2009-10-27 6:07 ` Ryan Hill
2009-10-27 7:02 ` Mike Frysinger
2009-10-27 13:09 ` Petteri Räty
2009-10-27 13:46 ` Mike Frysinger [this message]
2009-10-27 18:46 ` Petteri Räty
2009-10-28 2:31 ` [gentoo-dev] " Mike Frysinger
2009-10-28 9:51 ` Petteri Räty
2009-10-28 11:11 ` Alexis Ballier
2009-10-30 2:29 ` Doug Goldstein
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=200910270946.12243.vapier@gentoo.org \
--to=vapier@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