Hi Lisandro, Lisandro Damián Nicanor Pérez Meyer <perezme...@gmail.com> writes:
> Hi! > > On Wed, 4 Mar 2020 at 20:40, Nicholas D Steeves <nstee...@gmail.com> wrote: >> >> Hi Lisandro, >> >> Out of curiosity, could this be solved for a Debian (and derivatives) >> context by changing the Recommends on clang and clang-tidy to their >> versioned package names (eg: clang-8 and clang-tidy-8)? > > No, this is not a versioning problem. > I agree, ideally it should be solved upstream, but a side-effect of installing Recommends s/clang/clang-8/ is that it pulls in a dependency on libclang-common-8-dev, and Alexis Murzeau <amub...@gmail.com> writes: > Install `qtcreator` but not the `libclang-common-8-dev` package > Note: Installing `clang` package will install `clang-9` and not `clang-8`. > [snip] > > When installing the `libclang-common-8-dev` package, the clang code > model error goes away and no error is reported anymore. > [snip] > > I expect the clang code model to work out of the box with all depends > and recommends dependencies of `qtcreator`. > As of now, `libclang-common-8-dev` seems required by the clang code > model to work correctly, but that package is not a direct or indirect > dependency of `qtcreator`. > > The simplest solution (if it is the right one) is to add > `libclang-common-8-dev` as depends or recommends dependency to qtcreator. > Or maybe it should be a dependency of `libclang1-8` instead (which > qtcreator depends on). > My proposal would solve the Debian (and derivatives) case and is easy to update/maintain with a sed regex. Is our team categorically opposed to working around upstream issues using Debian packaging facilities? Thanks, Nicholas
signature.asc
Description: PGP signature
