DoDo

I tried your branch and when locking my project, I get hundreds of messages like these: ``` cpuinfo/20250509.9@microblink/main: WARN: risk: This package has 2 different dependencies on cmake_build/1.4.1@microblink/main with different...

> The good news is that apparently it didn't raise a conflict, so it seems it is good in that sense. True, but we fixed a lot of such conflicts...

> Could you please try again @DoDoENT and let us know? Still hundreds of warnings.

I still don't see any difference (I made sure to create a new venv and install from your branch with pip). Here is the output (I just executed the `lock`...

Now all warnings seem to be gone: ``` Connecting to remote 'microblink' with user 'dodo' conanfile_utils/1.0.13@microblink/main: Not found in local cache, looking in remotes... conanfile_utils/1.0.13@microblink/main: Checking remote: microblink conanfile_utils/1.0.13@microblink/main: Downloaded...

True, it's later in the output now. Like this: ``` $ conan lock create . Using lockfile: '/Users/dodo/Work/Microblink/core-blinkid-generic-recognizer/conan.lock' ======== Computing dependency graph ======== zlib/1.3.2@microblink/main: WARN: zlib/1.3.2@microblink/main: package_type 'static-library' is defined,...

It looks fine to me. However, I'd still be happier if non-visible dependencies (e.g., test dependencies) didn't even get propagated downstream...

Here is the smallest repro I managed to make: `base.json`: ```json { "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "base.json", "type": "object", "additionalProperties": false, "properties": { "data": { "$dynamicRef": "#concreteData" } }, "required": [...

OK, I had the same issue and installing `rsync` from homebrew and restarting both the shell and recreating the Xcode project and making sure that all derived-data folders are purged...

Maybe, in the name of hermeticity, `rules_xcodeproj` should ship its own `rsync`?