Summary: | [Future EAPI] Installed file-triggered postinst actions | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Michał Górny <mgorny> |
Component: | PMS/EAPI | Assignee: | PMS/EAPI <pms> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, freedesktop-bugs, gnome, pacho, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://wiki.gentoo.org/wiki/Future_EAPI/Triggers | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 174380 |
Description
Michał Górny
2016-11-12 11:42:07 UTC
(In reply to Michał Górny from comment #0) [...] > B. How often should those triggers be run? Do we want to run them after > every package, or just once at the end? Maybe that should be configurable > per-trigger? > For this case I think we will need to run it per package (as done currently from eclasses), to ensure the package is in a completely "installed" state. Otherwise we could have issues if other package going to be installed later needs something to be updated for being properly installed or run. > C. What about dependencies? Can we assume that relevant software (i.e. DEs > or something like that) will pull in the necessary packages eventually? Can > we assume that pkg_postinst/pkg_postrm of those packages will update/clean > up the caches appropriately? Or maybe should we store some kind of 'failed > to execute' state for triggers, and retry them later? > I think currently (from gnome eclasses point of view at least) we are trying to ensure the deps are installed usually from the package (in general the providers of the needed commands are so widely used that are present in most setups). Then, I would rely on proper RDEPENDs being pulled from the packages and a warning being shown by the package manager when it is unable to run a tool he pretends to run. That would help the maintainers to add the dependency if needed. > D. Do we need some degree of configuration per ebuild (i.e. disabling the > trigger in some ebuilds)? How to achieve that? I am not sure about any valid case for skipping the update of the caches... but probably I am missing some case :S |