[+gentoo-dev]

I'm just going to jump randomly in here.

Also, moving this back to -dev as it is not a private matter.

The bread and butter of this is what:

A. KDE team drops arch keywords for KDE 4, since KDE4 is new.

B. Jer re-keywords KDE4 on HPPA but doesn't try installing the
software to make sure it works.

C. Jer misses keywords because the KDE team did not provide a distinct
list of packages and Jer was relying on repoman to notify him when he
broke the deptree for HPPA.  Repoman has a bug/feature that caused it
to behave in an unexpected manner.

So I think most people think A. is an acceptable practice.  For all
intents and purposes KDE4 is new software.  Does anyone disagree with
this?

I think C is both Jer's and the KDE teams fault.  How difficult is it
really to produce a distinct package list KDE team?  You could always
refuse to keyword without such a list.

I think B is the real argument here.  Typically when commiting
packages you are supposed to install them and at least (in the case of
KDE) log into KDE and make sure it at least works.

Jer, did you do this?  If not; do you understand why the other
developers are upset?  Really I think they just want you to test
things you are keywording.

-Alec
-- 
[email protected] mailing list

Reply via email to