Zach Mitchell

``` $ cd $(mktemp -d) $ flox init -n has-pip $ flox install python313Packages.pip $ flox push $ flox delete -f $ flox activate -r zmitchell/has-pip ✅ You are now...

Update `flox show` output to list package outputs

6

Users need to see which outputs exist so they know which ones to specify in the manifest. Additionally, they need to know which ones are installed by default so if...

In an effort to surface the fact that packages have outputs and that users can choose to install specific outputs, we want to provide hints at installation time when a...

Regardless of whether we get this for free by virtue of the manifest being in the lockfile already, we need to keep track of which outputs were actually installed for...

A built artifact may only need certain package outputs at runtime, and this may be a different subset of outputs than you need during development.

Build environments with specific package outputs instead of all of them

1

We currently install every output provided by packages instead of the `outputsToInstall` attribute specified by the package. Packages from Nix provide "outputs", where one output may be a CLI, another...

We currently provide syntax for installing certain package versions on the CLI via `flox install foo@version`. This change would add syntax for installing specific outputs. Considerations: - Does our syntax...

If we provide the ability to install a specific package output, then we need a syntax to remove it. The syntax for uninstalling an output should match that for installing...

Specify outputs to install for package descriptors in the manifest

4

Example: ```toml [install] curl.pkg-path = "curl" curl.outputs = [ "bin", "man", "out" ] ```