On 01/27/2011 07:42 PM, Tomáš Chvátal wrote: > Only to gain the ~allarch. When it gains it gets tested by arch member > of any team and stabled. Verstanden? :)
Yep, I think I did. But what if introduce, say, a non-portable find command into a new revision that breaks on some arches. I'll carry over ~allarch for this revision, I even test it on my amd64 machine. Only to find prefix/bsd users screwed and wanting my head ;) So to continue having my stuff ~allarch, I'd need to post my modified ebuild to -dev again, right? Writing portable (shell) code is a lot harder than normal ebuild writing, as most of the issues won't come up on my machine and I'm simply not experienced enough with portability issues. So I'd find myself posting every change to -dev, just in case. So while the idea is intriguing, I think it won't help. Arch teams will have to recheck new revisions for conformance. The time taken to do this could be already spent on marking it "arch".
signature.asc
Description: OpenPGP digital signature
