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: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml
Date: Sun, 27 Mar 2011 09:37:00 -0600	[thread overview]
Message-ID: <20110327093700.5ff5f076@gentoo.org> (raw)
In-Reply-To: AANLkTimnhZ1Xjj+meRTickhDh_GOL7o-HdxGfj+=ZxGi@mail.gmail.com

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

On Sun, 27 Mar 2011 15:09:09 +0530
Nirbheek Chauhan <nirbheek@gentoo.org> wrote:

> On Sun, Mar 27, 2011 at 3:59 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> > On Sun, Mar 27, 2011 at 01:17:46PM +0530, Nirbheek Chauhan wrote:

> >> I propose that we should be more aggressive about package.masking (for
> >> removal) all maintainer-needed packages from the tree by doing that
> >> one month after they become maintainer-needed. If someone doesn't
> >> volunteer to take care of it, it probably wasn't important anyway.
> >>
> >>
> > Uhm no. The fact that nobody takes care of it doesn't necessarily mean
> > that the package is broken and that it should be removed
> >
> 
> I never said that such packages were broken. I'm saying that if no one
> wants to maintain them, they probably aren't needed by anyone, and we
> should clean such cruft from the tree.

This is just wrong.  If a package is working then it's easy to overlook the
fact it has no maintainer.  Nor does it need one.  When it breaks is when
people notice and either fix it or trash it.

> If they *are* needed by someone, then those folks should come forward
> to maintain it.

Good luck with that. :)


-- 
fonts, gcc-porting,                  it makes no sense how it makes no sense
toolchain, wxwidgets                           but i'll take it free anytime
@ gentoo.org                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:[~2011-03-27 15:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20110326055210.E906D20054@flycatcher.gentoo.org>
2011-03-27  4:45 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/PyZilla: PyZilla-0.1.0.ebuild ChangeLog metadata.xml Jeremy Olexa
2011-03-27  7:47   ` Nirbheek Chauhan
2011-03-27 10:29     ` Markos Chandras
2011-03-27  9:39       ` Nirbheek Chauhan
2011-03-27 13:04         ` Treeclean all maintainer-needed packages, was: " Chí-Thanh Christopher Nguyễn
2011-03-27 15:37         ` Ryan Hill [this message]
2011-03-27 13:30     ` Jeremy Olexa
2011-03-27 13:43       ` Nirbheek Chauhan
2011-03-27 19:17         ` Alec Warner
2011-03-27 19:40           ` Nirbheek Chauhan
2011-03-27 20:17             ` Alec Warner
2011-03-27 21:25               ` Nirbheek Chauhan
2011-03-27 23:34                 ` Ryan Hill
2011-03-28  1:59                   ` Donnie Berkholz
2011-03-27 20:44             ` Rich Freeman
2011-03-27 21:09               ` Nirbheek Chauhan
2011-03-28  1:58                 ` Donnie Berkholz
2011-03-27 21:28               ` René 'Necoro' Neumann
2011-04-05  4:26                 ` Jeroen Roovers
2011-04-05 10:58                   ` Alec Warner
2011-04-05 15:08                     ` Jeroen Roovers
2011-04-18 17:56                   ` Andreas K. Huettel
2011-03-27 13:44       ` Rich Freeman
2011-03-27 14:54         ` Tomáš Chvátal
2011-03-27 16:18           ` Rich Freeman
2011-03-27 14:08       ` Maintainership offering; was: " René 'Necoro' Neumann
2011-03-27 19:05         ` Jeremy Olexa
2011-03-27 20:20       ` Proxy maintainership of app-misc/pwsafe, was " Christopher Head
2011-03-27 20:47         ` Nirbheek Chauhan
2011-03-27 20:55           ` René 'Necoro' Neumann
2011-03-27 20:55           ` David Abbott
2011-03-27 21:32             ` Nirbheek Chauhan
2011-03-29 17:50       ` Dirkjan Ochtman
2011-03-29 13:33     ` Jeroen Roovers

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=20110327093700.5ff5f076@gentoo.org \
    --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