Allow the destination lib directory in prebuilt Dockerfile to be overridden

[chainchad]

Certain teams install shared libs in a directory other than /usr/lib.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[jinhoonbang]

thanks @chainchad . some questions:

1. what artifacts end up in the LIB_PATH_DEST directory? IIUC, the capabilities/plugin binaries goes to usr/local/bin right?
2. would it make sense to have usr/local/bin configurable as well? something like:

ARG FINAL_PLUGIN_DEST

# Copy plugins to /usr/local/bin
COPY ${PKG_PATH}/bin /usr/local/bin

# Conditionally copy to FINAL_PLUGIN_DEST only if it is set
RUN : "${FINAL_PLUGIN_DEST:=}" && \
    if [ -n "$FINAL_PLUGIN_DEST" ]; then \
        echo "FINAL_PLUGIN_DEST is set to '$FINAL_PLUGIN_DEST', copying plugins..."; \
        mkdir -p "$FINAL_PLUGIN_DEST" && mv /usr/local/bin/* "$FINAL_PLUGIN_DEST/"; \
    else \
        echo "FINAL_PLUGIN_DEST is not set, skipping plugin copy."; \
    fi

[chainchad]

Sorry, @jinhoonbang -- I just saw your comment.

what artifacts end up in the LIB_PATH_DEST directory?

The only use-case I'm aware of now is the libwasm share library.

the capabilities/plugin binaries goes to usr/local/bin right?

Right. This is the location that all of our binaries including chainlink get placed in the image at.

would it make sense to have usr/local/bin configurable as well? something like

We could absolutely do this but do you have a use-case or reason for needing a different bin directory?

[chainchad]

Closing as it turns out a custom lib path may not be needed after all. @jinhoonbang would need a custom bin path but it looks like he can update things on his side to work with the existing /usr/local/bin path for plugins.