Re: Removing shar(1)

Kyle Evans:
> I was reminded the other day that shar(1) exists, though it's use is no
> longer recommended in ports.  The same functionality can be found in tar(1)
> instead, so I think we should deorbit /usr/bin/shar and stop promoting it
> entirely.

for whatever it's worth (probably not much) i strongly disagree.
shar(1) has been around for ages and it does no harm to keep it.

>  It is easy to insert trojan horses into shar files.

half the software on the Internet nowadays tells people to do "curl |
bash" and we don't advocate for removing fetch(1) or sh(1).