Skip to content

--deploy-deps-only: Improve wording #321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tresf
Copy link

@tresf tresf commented Aug 22, 2025

Improve clarity, remove ambiguity about flag.
Related


Quoting history of this, from #305:

@tresf wrote:

Previously, I used -executable flag. Starting with linuxdepoy, I've tried both the --executable and the --library flags but I'm struggling to keep the expected layout.

@TheAssassin wrote:

[You should] make install the install tree to the AppDir, then use linuxdeploy with --deploy-deps-only to deploy the dependencies of the files in the subdirectories to usr/lib (while also setting their rpath accordingly, but without deploying the libraries themselves again into usr/lib). -l is meant for the manual packaging mode (e.g., when not using make install at all).
[...]
For libraries in directories passed to --deploy-deps-only, linuxdeploy sets the correct rpath and deploys their dependencies into usr/lib.

@tresf wrote:

Great this will fix the problem outright. Will [test and confirm]

@TheAssassin wrote:

I think the flag's help text explains this already: it is used on files already inside the AppDir.

@tresf wrote:

I agree in hindsight, but at first read, it was not obvious... [...]

@TheAssassin wrote:

Thanks for the improved wording. Could you send a PR, please?

Improve clarity, remove ambiguity about flag.
Related linuxdeploy#305
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant