public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Róbert Čerňanský" <openhs@tightmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-text/cuneiform
Date: Sun, 24 Mar 2013 10:15:57 +0100	[thread overview]
Message-ID: <20130324091557.ED2AB8B7870@amit.localdomain> (raw)
In-Reply-To: <m3y5dddgcz.fsf@carbon.jhcloos.org>

On Sat, 23 Mar 2013 16:13:07 -0400
James Cloos <cloos@jhcloos.com> wrote:

> >>>>> "MC" == Markos Chandras <hwoarang@gentoo.org> writes:
> 
> MC> The package is going away unless someone fixes the bugs and
> MC> properly maintains the package
> 
> Again, that is an irresponsible mistake.  It is better to just leave
> it as is than to kick it.  Dropping important packages can only harm
> the community and is never welcome.

And that is why I now appeal to users:

  _Do not report bugs to Gentoo unless a package is completely broken._

Because what you will get in return?  Package removed.

A package with bugs has a greater user value than no package at all.
Until Gentoo does not understands that and does not change its removal
policy accordingly, and provides technical means to reflect it*, it is
the only user-viable** way how to keep a package in the tree as long as
possible.

* Which could be e. g. masking a package until it is completely
  broken.

** No, I do not want to become a developer.  No, I do not want to
   maintain a package.  I am the user, I want using it.  (It does not
   mean that I do not contribute to the community, I just have other
   ways/projects to do so.)

Robert


-- 
Róbert Čerňanský
E-mail: openhs@tightmail.com
Jabber: hs@jabber.sk


  parent reply	other threads:[~2013-03-24  9:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 23:03 [gentoo-dev] Last rites: app-text/cuneiform Markos Chandras
2013-03-23 19:52 ` James Cloos
2013-03-23 20:06   ` Markos Chandras
2013-03-23 20:13     ` James Cloos
2013-03-23 20:21       ` Markos Chandras
2013-03-23 20:29       ` Rich Freeman
2013-03-23 21:40         ` James Cloos
2013-03-24  9:45           ` Rich Freeman
2013-03-24 13:02           ` Sergei Trofimovich
2013-03-23 21:33       ` Alec Warner
2013-03-24 13:24         ` Peter Stuge
2013-03-24 13:38           ` Rich Freeman
2013-03-24 13:52             ` Peter Stuge
2013-03-24 14:12               ` Rich Freeman
2013-03-24 14:35                 ` Peter Stuge
2013-03-24 14:54               ` Markos Chandras
2013-03-24 15:19                 ` Peter Stuge
2013-03-24 19:24                   ` Ian Stakenvicius
2013-03-24 23:40                     ` Rich Freeman
2013-03-25  7:05                       ` Róbert Čerňanský
2013-03-25  7:46                       ` Alec Warner
2013-03-24  9:15       ` Róbert Čerňanský [this message]
2013-03-24 10:43         ` Markos Chandras
2013-03-24 11:22           ` Rich Freeman
2013-03-24 12:11             ` Markos Chandras
2013-03-24 12:18               ` Rich Freeman
2013-03-24 12:31                 ` Markos Chandras
2013-03-24 12:40                   ` Rich Freeman
2013-03-24 14:48                     ` Markos Chandras
2013-03-25 10:22                       ` Ben de Groot
2013-03-24 19:00                     ` Róbert Čerňanský
2013-03-24 13:40               ` Peter Stuge
2013-03-24 13:48                 ` Rich Freeman
2013-03-24 14:14                 ` Alan McKinnon
2013-03-24 14:51                   ` Peter Stuge
2013-03-25  0:23                 ` Patrick Lauer
2013-03-25  0:26                   ` Rich Freeman
2013-03-25  3:17                     ` [gentoo-dev] " Duncan
2013-03-25  7:08                   ` [gentoo-dev] " Róbert Čerňanský
2013-03-25  6:25         ` Sergey Popov

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=20130324091557.ED2AB8B7870@amit.localdomain \
    --to=openhs@tightmail.com \
    --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