Hi folks,
just a little braindump, how revdep-rebuild could be made (partially) obsolete in future: Today it might happen that on an library update an old .so file gets unmerged while still used by somebody - that's what revdep- rebuild scans for. While it should catch those cases, we still have some downtime for certain packages (in bad cases, when it broke somewhere deep in the dependency chain, rebuild might take quite a lot of time). The main problem IMHO is that portage doesn't record which libraries some package links in, so it doesn't know which ones have to be protected from unmerge (unless explicitly stated somewhere). So I'd propose to add record that information. On next merge, this information can be used for an automatic library-protect. This would also record which libraries have been protected from removal and for whom. Subsequent merges will update this that, and once all importers have been unmerged, depclean can clean up the leftover dirt. What do you think about this idea ? cu -- ---------------------------------------------------------------------- Enrico Weigelt, metux IT service -- http://www.metux.de/ phone: +49 36207 519931 email: weig...@metux.de mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 ---------------------------------------------------------------------- Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme ----------------------------------------------------------------------
