Upstream Update: CLI11 1.7

[helmesjo]

Package Details

• Package Name: CLI11
• Latest available Version: 1.7

The above mentioned version is newly released by the upstream project and not yet available within Bincrafters. Please add this version.

[uilianries]

We have a deprecation note for that package:

https://github.com/bincrafters/conan-cli11/blob/stable/1.6.0/README.md

Package Deprecation Notice

The author of this library has taken ownership of the public Conan package for this library, which can be found at the following links:

CLIUtils/CLI11 bintray.com/cliutils/CLI11/CLI11%3Acliutils

Bincrafters will keep this version of the package on Github and Bintray for some unspecified amount of time (typically several weeks), however it will no longer be maintained or supported and will be removed without any further warning or notice. Users are advised to update their projects to use the official Conan package maintained by the library author immediately.

[helmesjo]

What is the idea in general? Looking at the magnum package, the author manages the conan script but the packages will be built & hosted by bincrafters. Though in that case the author specifically could not sacrifice CI-time to build packages.

Could a solution in cases like these (CLI11, where it is both maintained and hosted by the author) be that bincrafters host duplicates? That is: Automatically copy packages from maintainer -> bincrafters (triggered by new uploads)? My point is that it is extremely valuable/convenient to have as many packages as possible in the same repository (and from bincrafters they slowly move over to conan-center).

Thoughts?

[uilianries]

Good question! We discussed about deprecation here.

Though in that case the author specifically could not sacrifice CI-time to build packages.

Yeah, our Boost package could spend an entire day when building! So time is essential for us too.

Duplicated channel is not a good option IMO, we would need to replicate any fix and add new services to monitor any new change. I know it's annoying use different namespaces, but you could use conan alias.

Also, there is a documentation about "how to deprecate a package":
https://bincrafters.readthedocs.io/en/latest/contributing_to_packages/package_deprecation.html

[Croydon]

@uilianries You just copied the old depreaction text again in the readme

Bincrafters will keep this version of the package on Github and Bintray for some unspecified amount of time (typically several weeks), however it will no longer be maintained

😄

[Croydon]

Fixed :)

[Croydon]

Can we set an alias to the official recipe as well or do we still have some issues with that?

[uilianries]

Thanks @Croydon ! I copied from conan-cli11 README

We could create an alias as well, but is it really necessary? IMO we should avoiding alias, because bug related to official package could pointed to us by by unsuspecting users.