On Saturday, 05. January 2008 18:19:10 Luca Barbato wrote: > This thread so far spawned lots of reply from an external contributor > making the point of keeping stale ebuilds around and 4 developers > against the idea
Make that 5. > Anything other suggestions? Let the maintainer of said package decide on the keywording (and therefore how to handle slacker arches). An example: An arch cares more about e. g. games (and proudly blogs about it) than KDE. In such a case in the future I'm going to try to work it out with the respective arch and if they don't react in a timely manner, I'll simply remove the stale ebuilds (or whatever action is appropriate). And, if that has happened often enough, I will take appropriate steps to make sure such stuff doesn't happen again, e. g. by making sure the ebuilds I maintain are not keyworded by the respective arch again until their problems have been resolved. As will be the case for KDE4. It won't get any mips keyword. As for Ciaran's remarks - yes, theoretically, he is right but I don't see him arch testing for mips so his remarks are pretty meaningless to me. -- Best regards, Wulf
signature.asc
Description: This is a digitally signed message part.
