Hi Simon, Simon McVittie <s...@debian.org> (2020-09-03): > On Sun, 21 Jan 2018 at 21:27:47 +0100, Egmont Koblinger wrote: > > > We don't do c++ in d-i. > > > > Unfortunately this sounds really problematic. As of version 0.42 vte > > has been using (more and more) C++. This is not like Ubuntu's PCRE2 > > hack which is a matter of a few hours of work reverting and merging a > > few commits. It's reasonably impossible to revert to plain C and > > maintain that as a fork, and upstream has no intention to revert to C > > either. > > One way to resolve this might be to build the vte2.91 udeb with > -static-libstdc++, which makes it about 200K larger than it would > otherwise have been, but avoids needing a 1.5M shared libstdc++. vte > exports a C ABI, and only uses C++ internally. > > We need to upload a new vte2.91 to experimental anyway, so I'm going > to try this - d-i doesn't currently use that udeb anyway, so there's > nothing to lose by trying it.
This looks like a nice plan, thanks for the heads-up! Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
