Hahaha Thanks Theo, that made me smile. But you have answered my question perfectly, albeit in a round about way.
Indeed it doesn’t matter what it is called, and would be clearer with a generic name, as we got caught out by a program calling another program with colliding name. For example, Having ‘pkg_add’ call a program named ‘ftp’ to perform http and https downloads. But where errors in the ftp subprocess are printed by the pkg_add process, making it seem like pkg_add was failing on an ftp protocol request, rather than the ‘ftp’ client process failing (while doing an http call).. So I think it was pretty fair for us to end up scratching our heads ;) Thanks, Andy. Sent from a teeny tiny keyboard, so please excuse typos > On 30 Oct 2019, at 15:54, Theo de Raadt <dera...@openbsd.org> wrote: > > Andrew Lemin <andrew.le...@gmail.com> wrote: > >> To me this seems unusual (was expecting 'curl' or 'wget' etc to avoid code >> duplication) and confusing? What do you think? > > curl is not in openbsd > > wget is not in openbsd > > Maybe we should rename our downloading software to lemin, which is > obviously a randomly chosen name with some obscure acronym we'll invent > to back the name, being a name noone recognizes we can probably avoid > assumptions as to what it does, whether it does ftp, or http, or https, > or who knows what. Of course such a strange name would also lead people > to not discovering it, and make them install some monster software > package off the internet with another strange name. > > In summary I think it's turning into a shitty world with selection by > meme. > >