Frank Schoenmann

@MitchellBot Have you tried setting `CMAKE_BUILD_RPATH` to your sysroot (e.g. in a CMake toolchain file)? I think CMake does not usually add the sysroot to the RPATH as it is...

@MitchellBot That is correct (the sysroot I was refering to is part of the compiler/toolchain package). In our cross-compiler package, we have a `toolchain.cmake` file in the root of the...

What's the status of this PR? I'm running into this issue too.

@RubenRBS Thank you for the quick answer. I think I tried that (setting _user_ and _channel_ attributes in the conanfile) but I'm pretty sure it didn't work. I can check...

Really? That's too bad. There was even a recent [comment](https://github.com/conan-io/conan/issues/15629#issuecomment-1935120144) from memsharded that recommends using the `user` for differentiating packages that are not from ConanCenter. And as far as I...

> The reference for conan in the local recipe index will always match whatever the recipes in there have set, so unless you modify the conanfiles to have extra `user...

Thanks for the answer @memsharded. > Just in case, I have done a unit test to check if there was some functionality missing. I used `conan list -r local *`...

@dkoerner-festo That's true. But what would be your proposal? Setting the supplier is mandatory in our organization and (apparently) also for the US government, while the author is an optional...

@memsharded I'm aware of that but keeping our own version as close as possible to the "source" version here makes integrating upstream changes much easier. Not sure why no one...

> setting the supplier to Conan would not be correct for company internal packages. @dkoerner-festo I could use the `extension_properties` attribute to manually set a different supplier in the conanfile:...