Roman Gaufman wrote:
Heh, you obviously have failed to grasp that repoman still has to scan
hundreds of ebuilds, which takes a very long time, during which somebody
else might commit one of these ebuilds before repoman gets to it, thus
fouling everything up if you aren't at the computer to catch it. And
that is assuming my internet connection stays stable that whole time.
Fine, run repoman for every ebuild using a script as the above. Problem solved.
Uhh, that doesn't solve anything.
That and gentoo
policy states that each ebuild must be tested *first* before it can be
keyworded. If every dev went around keywording something because "it
should work", then we would be in a world of hurt.
You *are* testing each ebuild. By emerging kdemultimedia-meta -- you
must be emerging all those ebuilds. Same as you're testing all the
packages included with kdebase when you emerge the monolithic package.
No difference.
Read my last email, and stop being an idiot.
--
[email protected] mailing list
