I would suggest to use lang/erlang-runtime21 so that lang/erlang stays free for upgrades as the "user facing" Erlang, just in case..

I don't think users will get a warning when installing the package. I also don't think there is any change in the package, so bumping PORTREVISION is probably not necessary. @olgeni's suggestion?

I still think it's worth bumping the PORTREVISION to ensure everything
is rebuilt correctly. Erlang is picky about this, as explicit versions
are bound into the runtime configuration.

The original intent was to get this change sorted out before 2019Q3
starts which maximises time for users to get their stuff sorted.

In D20450#449537, @dch wrote:

I still think it's worth bumping the PORTREVISION to ensure everything is rebuilt correctly.

Yup - should definitely be bumped if moving to the -runtime version.

Bump?

Port builds fine for me, and I wombled my way through node startup without issue, but couldn't get auth working. I think the port is working fine, I just lack the leofs expertise. Mikolaj can you check it please before we push out the changes?

Looks like the port could do with a short pkg-message to explain how to set up your first node?

@dch the patch works for me.

I was creating a user for test with the commands:

leofs-adm create-user ${user} ''
leofs-adm update-user-role ${user} 9

And was using access-key-id and secret-access-key (outputed when leofs-adm create-user was run) in a s3 tool (s3cmd in my case).