On Sun, 16 Jan 2005 20:58:19 -0500, Stephen P. Becker <[EMAIL PROTECTED]> wrote: > Roman Gaufman wrote: > > Here is the same script, more human readable and configurable: > > > > P=kdebase-meta > > V=3.4.0_beta1 > > > > for i in $(cat /usr/portage/kde-base/$P/$P-$V.ebuild | grep -o > > "kde-base.*)" | sed 's/)//') > > do > > sed -i 's/~mips/mips/' /usr/portage/$i/`basename $i`-$V.ebuild > > done > > > > Enjoy, > > Roman > > > > > Keywording is a lot more than just adding the keyword to the ebuild. > Try running repoman 400 times (ouch!). Is this so hard to grasp? What > isn't hard to grasp, is that you have no idea what you are talking about. > > We know what we're doing, and we know that dealing with so many ebuilds > for a single desktop environment is much more trouble than it is worth, > especially when we would need to test them all in both big endian and > little endian installs over three different userland ABIs, as Kumba > pointed out, and you completely ignored. >
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. 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 > Steve -- [email protected] mailing list
