Hi folks,
just an idea spinning around in my head: Is it possible to influence the dependency resolution (eg. on virtuals) ? For example, several weeks ago somebody here asked on how to switch from jpeg to jpeg-turbo. For such cases it IMHO would be fine if there was some eselect which controls the behaviour of the virtual/jpeg package. Once he switched over via eselect, it would trigger the other jpeg implementation and (if necessary) rebuild of all depending packages on next emerge world. Could the current eselect + portage system provide this ? The whole idea could also be extended to packages which frequently require revdep-rebuild (eg. poppler): those packages would be slotted for parallel installation and an new virtual is introduced where clients will depend on (instead of the actual package directly) When new versions come out, the user will be tolld (eg. via eselect news) that he can now switch his system. Once he does the switch, new builds will be made against the new version and remaining packages (still linking to the old library) will be triggered for update. 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 ----------------------------------------------------------------------
