[aur-general] Tarball Guidelines

[keenerd]

Officially, the tarballs uploaded to the AUR should be named after
their package, contain a directory named after their package, contain
no dot files and most importantly contain no binaries.  Officially,
these requirements are very important.

Here are a bunch of non-conforming packages.  Maybe 90% of them.  (A
few errors slip though my scanner.)

Of the +700 packages with binaries, most are a simple desktop icon.
Should these be base64 encoded if someone can't find hosting?

If no one can think of a better way to deal with the nonconforming
packages, I'll write a bot to post insulting comments.  Personally, I
really like this solution.  The AUR has always had a wild west
frontier / insane asylum feel to it.  The less regulation, the better
it works.  But a few well placed suggestions could help make the two
thousand maintainers do a better job.

-Kyle

http://kmkeen.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aur-binaries
Type: application/octet-stream
Size: 9478 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20101203/695854e3/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aur-dotfiles
Type: application/octet-stream
Size: 1040 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20101203/695854e3/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: aur-badtar
Type: application/octet-stream
Size: 2149 bytes
Desc: not available
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20101203/695854e3/attachment-0005.obj>