Add multiple machines from one project example

[pavelzw]

There was still a "real world" example missing from the multiple machine use case.

Also, wouldn't this use case make the target table irrelevant?

The

[dependencies]
cmake = "3.26.4"
python = "3.10"

[target.osx-64.dependencies]
python = "3.11"

example also kind of goes against the philosophy of adding additional requirements to the requirements set (and not replacing them).

IMO the example above should be not solvable since python=3.10, python=3.11 together produce invalid requirements.

[ruben-arts]

I don't think this would remove the target feature completely as you might have small changes in package requirements without it needing a complete new environment that the user has to define in the cli.

If the user wants to get different versions for a package on another target then overwriting still seems valid to me. This is a common case with windows and linux for instance using different cmake versions or completely different build tools.

I would still want to keep this for now as you would need some smarter way of defining a feature to be auto selected. This is where cargos [target.'cfg("platform-name")'] notation would start to make sense.

[pavelzw]

Alright, then let's leave target be for now. What I personally don't like is that this now introduces two ways of basically doing the same thing.

[baszalmstra]

I think the example is missing minimal system dependencies!

Nvm.