How would this feature be useful?
Some packages have multiple dependencies that contain apps. When using --include-deps all these apps become globally available. This might lead to overshadowing of some of these apps if they are also in the PATH.
--include-deps should take a package name as argument in order to make only the apps provided by this package globally available
A concrete example is:
pipx install robotframework-keyta
pipx inject --include-apps robotframework-keyta robotframework-browser-batteries
Note: Dependent package 'robotframework-browser' contains 1 apps
- rfbrowser
Note: Dependent package 'grpcio-tools' contains 1 apps
- python-grpc-tools-protoc
Note: Dependent package 'robotframework' contains 3 apps
- libdoc
- rebot
- robot
Note: Dependent package 'seedir' contains 1 apps
- seedir
Note: Dependent package 'natsort' contains 1 apps
- natsort
No apps associated with package robotframework-browser-batteries. Try again with '--include-deps' to include apps of dependent
packages, which are listed above. If you are attempting to install a library, pipx should not be used. Consider using pip or a
similar tool instead.
In this case I would like to do the following:
pipx inject --include-deps robotframework-browser robotframework-keyta robotframework-browser-batteries
in order to only make rfbrowser globally available.
Describe the solution you'd like
Instead of being a boolean flag, --include-deps should take a package name as parameter and only make the apps provided by this package globally available
Describe alternatives you've considered
In the particular example above, a solution would be to first execute:
pipx inject --include-apps robotframework-keyta robotframework-browser
and then execute
pipx inject robotframework-keyta robotframework-browser-batteries
But this requires knowing in advance which package provides the app the user wants to execute.
Additional context
This feature has already been mentioned in #1673.
How would this feature be useful?
Some packages have multiple dependencies that contain apps. When using --include-deps all these apps become globally available. This might lead to overshadowing of some of these apps if they are also in the PATH.
--include-deps should take a package name as argument in order to make only the apps provided by this package globally available
A concrete example is:
In this case I would like to do the following:
in order to only make rfbrowser globally available.
Describe the solution you'd like
Instead of being a boolean flag, --include-deps should take a package name as parameter and only make the apps provided by this package globally available
Describe alternatives you've considered
In the particular example above, a solution would be to first execute:
and then execute
But this requires knowing in advance which package provides the app the user wants to execute.
Additional context
This feature has already been mentioned in #1673.