public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Maciej Mrozowski <reavertm@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Reworking package stabilization policies
Date: Mon, 29 Mar 2010 19:10:06 +0200	[thread overview]
Message-ID: <201003291910.06692.reavertm@gmail.com> (raw)
In-Reply-To: <1269847838.24530.80.camel@tablet>

On Monday 29 of March 2010 09:30:38 Peter Volkov wrote:
> В Вск, 28/03/2010 в 07:47 +0200, Maciej Mrozowski пишет:
> > No, seriously - given the fact that some of my packages were even
> > stabilized without contacting me (app-misc/hal-cups-utils,
> > app-admin/system-config- printer-common)
> 
> If you know packages are broken why they were not hardmasked? If they
> have no problems what why it was bad idea to mark them stable?

They are not broken, they're just not suitable. It's like stabilizing gcc-2.95 
now, even when it won't work with some recent KDE/boost.
hal-cups-utils is not a problem
system-config-printer-common-1.1.13 is as it's being used by maybe 
incompatible now system-config-printer-kde from testing arch (I've raised 
those deps now), besides I wanted to wait for polkit-1 with this package 
(otherwise dbus "newprinternotifications" can be received only by root or 
require tweaking dbus conf to work out of the box . That's why kde-
base/system-config-printer-kde and kde-base/printer-applet were intentionally 
left out from KDE-4.3.3 stabilization list.

-- 
regards
MM



      reply	other threads:[~2010-03-29 17:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 20:58 [gentoo-dev] reminding slacker arch's to handle bugs William Hubbs
2010-03-28  5:47 ` [gentoo-dev] [RFC] Reworking package stabilization policies Maciej Mrozowski
2010-03-28  6:31   ` Alistair Bush
2010-03-28  6:34     ` Brian Harring
2010-03-28  6:56       ` Alistair Bush
2010-03-28  9:43       ` [gentoo-dev] " Duncan
2010-03-28 20:35     ` [gentoo-dev] " William Hubbs
2010-03-28  7:39   ` Ciaran McCreesh
2010-03-28 10:04     ` Tomáš Chvátal
2010-03-28 11:32       ` Richard Freeman
2010-03-28 15:18     ` Maciej Mrozowski
2010-03-29  7:30   ` Peter Volkov
2010-03-29 17:10     ` Maciej Mrozowski [this message]

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=201003291910.06692.reavertm@gmail.com \
    --to=reavertm@gmail.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