The number of patches we have to disable various things or buildĪgainst system dependencies, I can't help but think we'd have anĮasier time keeping this package fresh if we could drop some of those. We actually *can* ship builds based on the bundled stuff. Legal/licensing considerations are still important and I don't know if Opinion, we should be pretty aggressive about dropping as many of theĬhromium patches as possible, even if that means we link against Up-to-date, which in turn will help us keep our users safer. Simplify the Chromium packaging will help us keep the package ![]() One lesson we may take from Mint, though, is that it's not worth trying Mint doesn't apply any patchesĪt all to the source, at least none of any real complexity. The biggest difficulty, as far as I can tell from my look at Chromiumįrom several months ago, is that our patch set needs a lot ofĪttention with every chromium release. The other things they build (NodeJS, and more). Well, you can start with the fact that the Mint chromium source packagesĭon't even include the chromium source, let alone the sources for all oldstable) as of now, but works fine at Sid in my (limited) experience. > Sorry for a silly question, but whatʼs so wrong with the build done by, so Debian needs a whole team to duplicate their effort? Itʼs for Debian 10 (i. The security team doesn't have the bandwidth to do it themselves, they need a team to help them. In my opinion, chromium deserves an active *team* to support it in Debian. > The problem really is lack of maintenance. > So what's happening with chromium in both sid and stable? I saw on d-release that it was removed from testing (#998676 and #998732), with a discussion about ending security support for it in stable. On Sun, at 07:58:17PM +0300, Dmitry Alexandrov wrote: Themselves, they need a team to help them. The security team doesn't have the bandwidth to do it We'll not ship it inīookworm unless we see steady uploads in unstable and we see security Impression support was picked up again, but alas). NotĮnough for stable (we shipped it in bullseye because we had the Over the past years, are just (more or less) incidental uploads. In my opinion, chromiumĭeserves an active *team* to support it in Debian. The problem really is lack of maintenance. Either way, both as a user and a developer, it is really not > ungoogled-chromium, #939406, if the plan is to have that in debian > time (or I could just as easily help with something like > to help out with chromium packaging if the problem is simply lack of > discussion about ending security support for it in stable. ![]() ![]() > d-release that it was removed from testing (#998676 and #998732), with a > So what's happening with chromium in both sid and stable? I saw on
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |