Remove porcelain dependency?

[hugomaiavieira]

The porcelain package is not been maintained very well, has knowing design flaws that can lead into zombie processes, and is showing some deprecation warnings on compilation.

Removing it will make this package dependency free (besides wkhtmltopdf of course). Also it will solve the hot code upgrading using distillery issue.

There is a specific reason to use porcelain? Couldn't we use the built in System.cmd/3 function?

TODO: read more about Port module, the zombie processes, and the porcelain's basic driver to try to answer the questions above and create an issue on the original repo.

[gutschilla]

Excuses

@hugomaiavieira You're right about Porcelain. Back in 2015, when this module came to life, Porcelain was the easiest way to get something started without needing to dig into the ports (The documentation was, well, like this: https://hexdocs.pm/elixir/1.0.5/Port.html#summary). Initially, I didn't want to use temporary files – but then I got it trivially easy working with so I kept it that way.

The bright future

I guess, Ports will do. Just need time to do it ;-)

[hugomaiavieira]

Thanks for the info @gutschilla! :)

[hugomaiavieira]

gutschilla#44