Conan Repository Exclusive May 2026
conan remote update my-private --allowed-packages="boost/*, openssl/*, internal/*" conan remote update conan-center --allowed-packages="*" --exclusive=False When you create a package, you can "bless" it as exclusive to a specific repository. This prevents developers from accidentally uploading a package with the same name to a different repo.
When you generate a lockfile in a repository-exclusive environment, Conan writes the exclusive remote name into the lockfile. Later, when another developer runs conan install --lockfile=conan.lock , Conan will and fetch exclusively from the remotes listed in the lockfile. conan repository exclusive
Conan operates on a "first-found, first-used" principle. By default, if you have multiple remotes (e.g., conan-center , my-company-private , dev-local ), Conan will search them in order. However, the feature overrides this behavior. However, the feature overrides this behavior
This article will explore what the "Conan repository exclusive" means, why it matters for enterprise teams, how to configure it, and how to troubleshoot common pitfalls. To understand the term, we must first break it down. In Conan, a repository (often called a "remote") is a server that stores Conan packages (collections of binaries, source code, and metadata). An exclusive in this context refers to a locking mechanism or a routing directive that forces Conan to look for—or store—a specific package recipe or binary in only one specific repository , ignoring all others. ignoring all others.