configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 9.9 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 100 10 Systems and cross case) Or you can have a very widely used option in many packages and set its value all at once with patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 6 it in the [read_permissions] and [write_permissions] sections. These sections allow a sequence of patterns and allowed users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 12.8 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 180 13 Systems and cross the [read_permissions] and [write_permissions] sections. These sections specify the sequence of patterns and authorized users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel: files (e.g the xx-config.cmake files from the CMakeDeps) will be created. • self.patterns: Describe the file patterns of your source and build folders. It will ease the process of pack- aging the files

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 12.8 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 180 13 Systems and cross the [read_permissions] and [write_permissions] sections. These sections specify the sequence of patterns and authorized users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel: files (e.g the xx-config.cmake files from the CMakeDeps) will be created. • self.patterns: Describe the file patterns of your source and build folders. It will ease the process of pack- aging the files

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 12.8 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 180 13 Systems and cross situations whereby many packages use the same option, thereby allowing you to set its value once using patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 52 the [read_permissions] and [write_permissions] sections. These sections specify the sequence of patterns and authorized users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 12.8 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 182 13 Systems and cross situations whereby many packages use the same option, thereby allowing you to set its value once using patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 52 the [read_permissions] and [write_permissions] sections. These sections specify the sequence of patterns and authorized users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 12.8 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 182 13 Systems and cross situations whereby many packages use the same option, thereby allowing you to set its value once using patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 52 the [read_permissions] and [write_permissions] sections. These sections specify the sequence of patterns and authorized users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 9.9 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 104 10 Systems and cross situations whereby many packages use the same option, thereby allowing you to set it’s value once using patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 5 the [read_permissions] and [write_permissions] sections. These sections specify the sequence of patterns and authorized users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 10.9 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 106 11 Systems and cross case) Or you can have a very widely used option in many packages and set its value all at once with patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 6 it in the [read_permissions] and [write_permissions] sections. These sections allow a sequence of patterns and allowed users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 10.9 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 108 11 Systems and cross You can also have a very widely-used option in many packages and set its value all at once with patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 6 it in the [read_permissions] and [write_permissions] sections. These sections allow a sequence of patterns and allowed users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel:

configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 9.9 Conan local cache: concurrency, Continuous Integration, isolation . . . . . . . . . . . . . . . . . . . 104 10 Systems and cross You can also have a very widely-used option in many packages and set its value all at once with patterns, like: $ conan install . -o *:shared=True Any doubts? Please check out our FAQ section or . 5 it in the [read_permissions] and [write_permissions] sections. These sections allow a sequence of patterns and allowed users, in the form: # use a comma-separated, no-spaces list of users package/version@user/channel: