Re: CVS commit: src/usr.bin

[christos%astron.com@localhost (Christos Zoulas)]

In article <20180724185738.GA15885%britannica.bec.de@localhost>,
Joerg Sonnenberger  <joerg%bec.de@localhost> wrote:
>
>Why do we need another base64 encoder/decoder?

So I've been looking into how to get rid of it and re-use uuencode
uudecode for it and it is proving difficult. I am trying to provide
a command line compatible utility with the "base64" command from
MacOS/X and Linux:

- They use a single command to encode and decode (uuencode and decode
  are two separate programs). I would have to either write a shell
  script front end (and modify them not to output a header) to be
  able to emulate that.
- uudecode is using b64_pton() which does not handle arbitrary whitespace.

I could merge all three into one, but this is more annoying and risky
to break things due to the amount of legacy behavior in the uu commands.

Any better options?

christos