> (Also, I'm really not sure why having the port installed would interfere with building a new one, but I've always built Erlang with make and erlc which is may

> (Also, I'm really not sure why having the port installed would interfere with building a new one, but I've always built Erlang with make and erlc which is maybe a bit unusual) It looks like this happens because the ejabberd is installed into system's erlang lib directory and that impacts the build process. I'm wondering why author of the port opted to force un-installation instead of just install it in another directory? Is there a benefit of doing it this way? I was thinking to suggest that, but I don't know enough about erlang if that even makes sense.