Summary: | trap hook | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Luigi 'Comio' Mantellini <luigi.mantellini+gentoo> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | CC: | alex_y_xu |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Luigi 'Comio' Mantellini
2006-06-24 15:35:06 UTC
Do we want to support this? I'm curious about what some of the use cases will be for the proposed hooks. Most of our ebuild.sh traps are pretty useless and I'd like to remove them (or replace them with hooks if that's really useful). The only trap that currently seems to do anything useful is the SIGTERM trap which is used to implement support for die in a subshell. checking my portage-2.2.18 ebuild.sh, there appears to only be a SIGTERM trap. SIGTERM needs to be trapped for die to work, and the only standard utility that generates it is "kill" which can be easily modified to generate another signal. |