llama-stack-mirror/llama_stack/cli
Charlie Doern 268766c72e feat: group deps by provider
dependencies are currently installed and listed in an unassociated way with the provider they come from.

From a user POV, associating deps with the specific provider introducing them is crucial in order to eliminate unwanted dependences if using a larger distro like starter.

For example, If I am using starter on a daily basis but then go `llama stack build --distro starter...` and get 15 NEW dependencies, there is currently NO way for me to tell which provider introduced them.

This work fixes the output of the build process and `--print-deps-only`

Signed-off-by: Charlie Doern <cdoern@redhat.com>
2025-08-20 16:33:58 -04:00
..
model chore(rename): move llama_stack.distribution to llama_stack.core (#2975) 2025-07-30 23:30:53 -07:00
scripts API Updates (#73) 2024-09-17 19:51:35 -07:00
stack feat: group deps by provider 2025-08-20 16:33:58 -04:00
__init__.py API Updates (#73) 2024-09-17 19:51:35 -07:00
download.py chore(rename): move llama_stack.distribution to llama_stack.core (#2975) 2025-07-30 23:30:53 -07:00
llama.py chore: more mypy fixes (#2029) 2025-05-06 09:52:31 -07:00
subcommand.py API Updates (#73) 2024-09-17 19:51:35 -07:00
table.py chore: enable pyupgrade fixes (#1806) 2025-05-01 14:23:50 -07:00
utils.py chore: rename templates to distributions (#3035) 2025-08-04 11:34:17 -07:00
verify_download.py chore(rename): move llama_stack.distribution to llama_stack.core (#2975) 2025-07-30 23:30:53 -07:00