. . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they want to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they wants to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 87 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they wants to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they wants to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they wants to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 89 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they want to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they want to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 91 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they want to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 8.3 Build requirements . . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they want to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local

. . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.2 Creating conan packages to install dev tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 8.3 Build requirements . packages directly from these source and build folders, though conan package is still recommended in the dev-flow to debug the package() method. • Using the package-folder argument (incompatible with the above but at the same time they want to work on cool/version@user/dev library which is tightly coupled to the app. The package cool/version@user/dev is already working, the developer has the sources in a local