> Also, know that we are now resolved to make [community] and the > unsupported collection accessible via cvsup, so that you can fetch the > whole thing cleanly at once. Hopefully that will be a better solution > than aurscrape -- which is effective.. don't mean to disparage it.. but > inefficient.
Heh, yeah aurscrape was a crappy crappy way to grab everything... I didn't mean for it to be good 8) > Integration with ABS wholesale is a different topic. We won't > support/suggest that anyone actually use ABS or srcpac to build packages > in the unsuppported collection; this is just a patently bad idea. It's > possible that nobody has reviewed those PKGBUILDs, and it's possible the > devil himself has submitted them. What about having them come across as, say, PKGBUILD.aur or something, so you need more than a simple "makepkg" to build it (I believe it's the -p flag?) > I find myself strangely attracted to the idea of a CLI for searching > unsupported, like what "pacman -Ss" does across repos. This won't be > easy but maybe in a later release. This would require something akin to an unsupported.db.tar.gz, which can't really be generated as is, unless you do it manually (sounds fun, I may look into it, though I be Xentac could do it in 5 minutes) > We realize that right now the concept of a TU is not well defined, and > the process for becoming one is intimidating. So I'd like to start a > discussion on how we could improve the process and get more people who > would make good TUs on board. The two things you most need to do to be a > TU are: 1) be someone we can trust and 2) be someone who understands the > packaging guidelines inside out and is meticulous. Why are these > requirements? Because you'll be deciding on behalf of the community what > binary packages go into [community] and then go on to people's Arch > boxes and get run. My opinion was always this: if a user is to be trusted, why is he not voted in by the community... why is he voted in by a small group (subset? superset?) I think, if the term is to be "trusted" user, then the users should vote for them if they apply... I don't know how this would work, or how it would be implemented (in the AUR?), but it's just my idea. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
