I was under the impression repoman can commit changes to tree, not per ebuild. In any case, feel free to edit the script to run repoman for you. I'm sure it will finish over night without your presence at the PC. - so no trouble at all.
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.
I still have no idea how its any different to testing kdemultimedia instead of kdemultimedia-meta in big endian and little endian installs over three different userland ABIs. As far as I can tell, there isnt a single difference.
Roman
Time and resources. I already told you multiple times that splitting kde up so would cause kde to take way longer to emerge, even if/when proper confcache support is added, which it hasn't. 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. Besides, you are obviously not a gentoo dev or a mips user, so what do you care?
Steve
-- [email protected] mailing list
