[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#904688: qttools-opensource-src: FTBFS: please drop the libclang-dev B-D on some architectures



2018-07-27 14:48 GMT+02:00 Lisandro Damián Nicanor Pérez Meyer
<perezmeyer@gmail.com>:
> El viernes, 27 de julio de 2018 09:24:46 -03 Manuel A. Fernandez Montecelo
> escribió:
>
> [snip]
>> This page states that:
>>
>>   http://doc.qt.io/qt-5/gettingstarted.html
>>
>>   Note: From Qt 5.11, QDoc requires clang from LLVM 3.9 for parsing C++
>>   header and source files, and for parsing the function signatures in
>>   \fn commands. See Installing clang for QDoc for details.
>>
>> However, if it can be built without these doc tools, for example using
>> Adrian's patch, it would be very nice to try.
>>
>> Not sure if it will break many packages (for these arches), packages
>> might assume that qdoc tools are there, but the alternative is at least
>> equally bad, and potentially worse.
>
> It will also mean that we Qt maintainers will start receiving valid bugs.
> Considering the ratio of work and manpower we have now it's not something we
> would like to deal with. Now if you can somehow chime in here, well, we can
> make an arrangement of some type I guess.
>
> Maybe by opening a bug due to qdoc removal on some archs might help, you could
> subscribe there if needed.

OK, sounds fair, whatever the solution is implemented.

I was using codesearch.d.n and there are 83 that match "qdoc":
https://codesearch.debian.net/search?q=%5CWqdoc%5CW

Probably not all of these will actually use it for building (maybe
they will only test if available, and will generate an empty package
or something), others might do it only on -indep as Adrian says.
Almost certainly it will break some package.

At that point we can intervene and explain to maintainers, or provide
patches, for them to build it as -indep, so it's a win also for the
wide Debian project (building -indep when possible, saving resources,
etc).

-- 
Manuel A. Fernandez Montecelo <manuel.montezelo@gmail.com>


Reply to: