❦ 14 December 2021 09:13 GMT, Jeff Blake:
> Unless there are licensing or technical objections, I would suggest building
> with upstream
> bundled clang to avoid all sorts of incompatibilities and obviate the need
> for extra patching
> (stable's clang is often too old and upstream currently uses clang-14 vs
> unstable's 13).
> As an added bonus, this is a prerequisite to, and allows building with PGO
> enabled. Refer to
> my rules file to see how download of upstream clang/llvm binaries can
> be automated [6].
Unfortunately, packages are not allowed to fetch external stuff during
build. You'll need to vendor clang, either directly in the source
tarball or as an additional tarball.
I just cite this part, but I agree with everything else you said.
> Finally, it's good to see some of the maintainability issues being
> discussed, as when debian chromium development was restarted a year or
> so ago, I became frustrated when my questions on the issue went
> unanswered. So many patches seemed to be superfluous, yet nobody
> seemed to have the motivation, authority or courage to delete them.
The situation didn't change that much. When a maintainer is inactive, it
is always a bit difficult to know how to move forward. The issue has now
gotten a bit more light, but it is still unclear on how to proceed. I
don't think we had a similar case in the past (pretty popular package,
totally unable to push security fixes). It is a pity the package got an
exception to go in Bullseye while it was pretty clear we would get into
this situation.
--
As flies to wanton boys are we to the gods; they kill us for their sport.
-- Shakespeare, "King Lear"
