Ok, I sat back and watched for a while, but perhaps I'll speak up now. My 'ideal' solution to this issue is a complicated one, though I don't think it's all that hard to implement (maybe). I'm thinking about something along the lines of a trust model of some kind, where you have to add a certain user to a "trusted" list. When one goes to run srcpac (or whatever tool we might concoct to handle all this), it checks the maintainer of the package you're trying to get. If the maintainer is on your trusted list, it could build silently, while if the maintainer is not on the list, it stops, and tells you to go read the PKGBUILD. Once you have read through it (presumably) you could maybe pass in a certain command line option that suppresses the stop, or how about being able to make the trust list even package-specific?
I dunno, might be a messy or overly-complicated solution, let me know what you think. -Simo
signature.asc
Description: This is a digitally signed message part
_______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
