I really do not understand why you discuss count of my packages and why I should move some of them to unsupported.<br><br>Not only I have community packages with low votes.<br><br>Let us make _exact_ rules when TU can move package to community and when can not.
<br><br>We may have long discussion about NOLIBTOOL (which can be successfully recognized by makepkg with warning), maintainer tag or license, package upgrade time after new version released, but it is not constructive.<br>
<br>Constructive way, I think, is notify me about problems (which already done in this thread) or make _exact_ rules and make ALL TUs (not me only) execute it.<br><br>PS - I&#39;ll replace all old options=() in whole community soon with a script.
<br><br>PPS - I&#39;ll recheck all my packages for license field and I&#39;ll check last ~100 pkgs for #Maintainer tag<br>