What package calls pango-view? Is it missing a runtime dependency on the pango package? I only removed chromeos-chrome's dependency on it, so it probably shouldn't have disappeared if dependencies were specified correctly.

Uploaded https://chromium-review.googlesource.com/c/441117/ to add a dependency to common-assets. Is there a factory package that needs similar treatment?

Re#2: So you are ok with pangi-* still living in system? I was wondering if your goal is to eliminate pango from base image.

If pango is ok to keep, then it's very easy to solve. As you have made changes to 441117, I can also change the factory packages for it.

Thanks!

P.S: After looking at source, factory code was made to allow display_boot_message to run, not using pango directly; so I think your 441117 is all what we need.

(There are some other dead factory code using pango directly but I believe we can delete them)

I'd love to still remove our use of pango, cairo, glib, etc., since it's weird to ship graphics libraries that aren't used by Chrome, and since glib is a poor choice for C++ code when we have STL and libchrome available.

I don't want to break stuff while figuring out how to do that, though, and we need to specify dependencies correctly so that it doesn't happen inadvertently. If you already know which factory packages need to be updated, please do it. :-)

(To the bigger question of how to remove pango, maybe it'd be possible to build a small binary that uses Skia to render these messages. I'll save that for another bug, though.)

Re#8

Yes I agree. I think you just need to make sure display_boot_message is working fine then factory code will be good (or at least just few minor changes)

(Even better if your new approach can provide an approach for showing a list of all its  runtime dependency since factory code was trying to copy the files into a tmpfs for wiping - and that's why we invoked pango-querymodules)

https://chromium-review.googlesource.com/c/441117/ is in.