How to avoid /usr/local/bin/_internal on linux?

[zapta]

We created installer onedir binaries for our command line app and packed it as a Debian package. To make it work we keep the my-app binary and the _internal directory in the same directory, which results after installation in having this directory structure:

/usr/local/bin/my-app  
/usr/local/bin/_internal 
...

This works but having a generic name _internal in a common directory such as /usr/local/bin is sub optimal because it's not clear what _internal represents and it will conflict with future pyinstaller apps that are created in the same way.

Is there a way to rename _internal to something like my-app-internal, or to move it to a subdirectory that contains the name my-app.?

EDIT: Having _internal in /usr/local/bin also results in many lintian errors. For example

E: apio: dir-in-usr-local [usr/local/bin/_internal/]
E: apio: dir-in-usr-local [usr/local/bin/_internal/apio/]

[bwoodsend]

/usr/local isn't really a suitable place for whole dependencies-included applications. It's also supposed to be reserved for non system package manager usage so .deb/apt shouldn't be touching it.

I'd expect the application to install into /opt then create a symlink to the executable from /usr/bin.

[zapta]

Thanks @bwoodsend. ChatGPT agrees with you.