[aur-general] Policing AUR content (Was: Handling coincidental name collisions)

[Brett Cornwall]

On 2019-02-09 14:49, Xyne wrote:
>On 2019-02-09 14:36 +0100
>alad via aur-general wrote:
>
>>The "original" lsf looks like a joke/troll package to me, rather than
>>"trivial". I'd have deleted it even without community duplicate.
>>
>>Alad
>
>To me it just looks like the package of someone discovering bash programming
>with ANSI escape codes and wanting to share. The fact that it's on github with
>a README.md and a preview is an argument against it being a joke/troll.

Agreed. This is pretty clearly not a troll package. It's an easy-to-run 
script that could easily be featured in one of those 'Top 5 things the 
Linux terminal can do' articles.

>The discussion is important because we need to have a general consensus on
>deletion criteria. Rogue TUs can't be allowed to roam the AUR deleting whatever
>they personally don't find useful on a given day.

"All art is quite useless." -Oscar Wilde

I'd propose that malicious/spam packages get deleted in this manner, and 
nothing else. We can't police what people want to do with their 
installation. Scripts like this may be trivial but they're bound to give 
enough people joy. Occasionally I zen out to asciiquarium (admittedly a 
much more involved program but no more useful than lsd) every now and 
then.

The point is, it was a legitimate program and should be welcomed in the 
AUR like any other (with the naming conflicts resolved).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/aur-general/attachments/20190209/732b4300/attachment.sig>