James

> For the use case of packaging pre-compiled binaries, this means downloading binaries for all platforms in source() and then using package() to only package the one for the target...

Great. I will move this to the docs to improve that sentence (though new Conan 2.0 might happen earlier than it). Thanks!

Hi @frank-xlj The key here is the ``version-ranges`` installation. Doing something like ``` conan install zstd/[^1.0.0]@ --update ``` Internally does a search in the server for the ``zstd/*`` package versions,...

> But when we use 1.30.2, it just reported "ERROR: Version range '1.0.0' from requirement 'mypkg/[1.0.0]@aa/stable' required by 'virtual' could not be resolved in local cache.", didn't even search any...

@tthef sorry, I didn't get it, the test is relatively straightforward, version-ranges shouldn't resolve to a package with different or no user channel, if you depend on ``requires = "pkg/[>1.0]@myteam/stable"``,...

Hi @prietomj The truth is that the Conan cache has never guaranteed concurrency. While it tried to provide some protections for concurrent usage for some specific use cases, it was...

Sorry this was never reviewed or managed. Unfortunately, this ``Git`` tool has been superseded by ``from conan.tools.scm import Git`` new one, so these docs are no longer necessary. Thanks!

Hi @CaptnMorgan833 You mean that you have asset files in the template? That is interesting, why would you be including the same image files in the conan package recipe files,...

I can't reproduce, it seems to be working fine, this is the test unit I wrote: ```python def test_template_image_files(self): client = TestClient() template_dir = "templates/command/new/t_dir" save(os.path.join(client.cache_folder, template_dir + "/myimage.png"), "$&()")...

Oh, that could be it, indeed, the template feature improved recentely, the directory case was not handled before. I'd suggest trying to upgrade.