Bah!
for i in $(cat kdebase-meta-3.4.0_beta1.ebuild | grep -o "kde-base.*)" | sed 's/)//'); do sed -i 's/~mips/mips/' /usr/portage/$i/$i-3.4.0_beta1.ebuild ; done
There, a simple 1 liner I wrote in 10 seconds to properly keyword all packages owned by kdebase. Where is the problem?
You are testing the *same* 15 packages, i.e. emerge kdemultimedia-meta. -- Only difference is you are given the option to save hours by not compiling things you dont want to test. Feel free not to use that option though.
Is this so hard to grasp?
I've always grasped the concept of keywording multiple packages in rapid fashion.
What you fail to grasp is proper QA. As a developer, one does not just go keyword happy and commit to CVS - One has to test *each* and *every* package, otherwise, bad things can happen.
With monolithic KDE, we can test & keyword something like kdenetwork. That covers a number of packages in one sweep. With the split ebuilds, we now have to test and keyword each ebuild *individually* -- this consumes more time, but is necessary to stick to QA guidelines.
Sure, it's the same XX ebuilds that we have to test between the monolithic and split forms of KDE, and yes, chances are if a package in the split form breaks, it'll also break in the monolithic form, so one would think that what I argue is a moot point. In a perfect world, it is a moot point, but alas, in a perfect world, many things would be different and/or better. QA is there for a reason, and if a dev skimps on it, we generally find the RepoMan and Mr. Bones waiting outside our front door the following morning.
--Kumba
--
"Such is oft the course of deeds that move the wheels of the world: small hands do them because they must, while the eyes of the great are elsewhere." --Elrond
-- [email protected] mailing list
