1 |
On Monday 29 of March 2010 09:30:38 Peter Volkov wrote: |
2 |
> В Вск, 28/03/2010 в 07:47 +0200, Maciej Mrozowski пишет: |
3 |
> > No, seriously - given the fact that some of my packages were even |
4 |
> > stabilized without contacting me (app-misc/hal-cups-utils, |
5 |
> > app-admin/system-config- printer-common) |
6 |
> |
7 |
> If you know packages are broken why they were not hardmasked? If they |
8 |
> have no problems what why it was bad idea to mark them stable? |
9 |
|
10 |
They are not broken, they're just not suitable. It's like stabilizing gcc-2.95 |
11 |
now, even when it won't work with some recent KDE/boost. |
12 |
hal-cups-utils is not a problem |
13 |
system-config-printer-common-1.1.13 is as it's being used by maybe |
14 |
incompatible now system-config-printer-kde from testing arch (I've raised |
15 |
those deps now), besides I wanted to wait for polkit-1 with this package |
16 |
(otherwise dbus "newprinternotifications" can be received only by root or |
17 |
require tweaking dbus conf to work out of the box . That's why kde- |
18 |
base/system-config-printer-kde and kde-base/printer-applet were intentionally |
19 |
left out from KDE-4.3.3 stabilization list. |
20 |
|
21 |
-- |
22 |
regards |
23 |
MM |