Am sort of OK with this if others are but cautiously as it's a bit weird to have the uses_from_macos marker only on Linux because Linux happens to be the one picked. Linux itself shouldn't have to care what macOS system dependencies are.

Do we even know that deterministically Linux is always picked with all bottles? It might just be alphabetical and break if a name like Yosemite returns.

I am not sure what this is. Did you mean that Linux runners do not check bounds (and keg will use the system's prefix even if since: :<higher_macos_version> is set)?

I wasn't talking about since: but good point as this will be incorrect for that.

all bottles are produced by effectively picking one of the OS bottles and tabs and using that. Which one is used is not defined but probably happens to be x86_64_linux. runtime_deps_hash is also only called with actual runtime dependencies - so any uses_from_macos is omitted on platforms that use the system:

Here's what the tab would output with this:

{
  ...
  "runtime_dependencies": [
    {
      "full_name": "perl",
      ...
      "declared_directly": true,
      "uses_from_macos": false,
    }
  ],
  ...
}

{
  ...
  "runtime_dependencies": [],
  ...
}

{
  ...
  "runtime_dependencies": [
    {
      "full_name": "perl",
      ...
      "declared_directly": true,
      "uses_from_macos": true,
    }
  ],
  ...
}

{
  ...
  "runtime_dependencies": [],
  ...
}

{
  ...
  "runtime_dependencies": [
    {
      "full_name": "perl",
      ...
      "declared_directly": true,
      "uses_from_macos": true,
    }
  ],
  ...
}

The last case definitely being incorrect for <= Sonoma if we are checking for uses_from_macos.

In the end it's a fundamental problem with using runtime_dependencies in all bottles. The exact same could happen with on_macos or on_linux blocks. We do have code that works around it but it applies too late for this particular case:

@botantony please hold off opening any more PRs until the existing ones are merged, thanks

Am sort of OK with this if others are but cautiously as it's a bit weird to have the uses_from_macos marker only on Linux because Linux happens to be the one picked. Linux itself shouldn't have to care what macOS system dependencies are.

Agreed. It's also unclear to me how/whether this is perl specific.

In the end it's a fundamental problem with using runtime_dependencies in all bottles.

@Bo98 maybe we should just throw it away at either bottle and/or installation time and regenerate it?