Re: pkgsrc-wip: misc/DeepSeek-TUI renamed to misc/CodeWhale; editors/fresh 0.3.12

[Greg Troxel <gdt%lexort.com@localhost>]

David Holland <dholland-pkgtech%netbsd.org@localhost> writes:

> Then there's another entirely different but also important question,
> which is if upstream starts embracing slop to the point where it
> becomes a problem for us (e.g. adding vast quantities of cutpaste slop
> that only builds on Linux), what if anything we should try to do about
> it.

I sympathize, but I think it's like other low-quality code.  What if
somebody writes to the man pages no their bleeding edge GNU/Linux
system, and ignores basic portability?  It's basically the same mess
with a dose of unreviewable.

If somebody wants to package linuxslop with BROKEN_EXCEPT_ON=Linux, then
I don't feel that I should try to stop them.  I can see us removing a
package if we get to "we're getting bugs about it and nobody is willing
to touch it".   I can see that we might end up with concerns about
embedded malware and decide it's too dangerous, and rename the package
to -bin to denote that it's not really source code.