Zach Mitchell

Do we need to bump the manifest version?

May also need a way to specify different outputs for different systems

In the case that you want different outputs for different systems, you can do something like this: ```toml [install] linux-curl.pkg-path = "curl" linux-curl.systems = [ "aarch64-linux", "x86_64-linux" ] linux-curl.outputs =...

That doesn't seem to do the trick. Just to be concrete, let's say I have this type: ```rust #[derive(Debug, Error, Diagnostic)] #[error("Invalid manifest")] #[diagnostic( code("manifest::parse"), url("http://example.com"), help("Please check the documentation...

I see, I guess I was confused why I needed to call `into_diagnostic` on something that already impls `Diagnostic`

It looks like `process-compose` allows configuring its timestamp format by setting a config value to one of these Go standard library values: https://pkg.go.dev/time#pkg-constants

I opened an upstream issue to allow configuring the timestamps of the internal logs: https://github.com/F1bonacc1/process-compose/issues/375

Similar issue, but the opposite symptom. Setup: 1. Activate a default environment in `.zprofile` and `.zshrc` 2. Create a new environment that does auto-setup: ``` $ cd $(mktemp -d) $...

> The suggestion Are you saying that this is the suggestion from upstream, from @tomberek, or that we should install `corepack` when we install `nodejs`? I'm having trouble parsing this...

I think there is some confusion in the responses to this ticket. The original issue looks like `corepack` failing because it's attempting to create a symlink in the Nix store,...