Scriptlet args
Package scriptlets will get more information (e.g. NEVRA of the packages) about currently run transaction in environment variables. This will make it easier for scriptlets to handle special situations or to detect more precisely what is happening. (One could for example convert some config files when upgrading from package of version 1.x to 2.x and to leave them intact otherwise).
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Jeff Johnson
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Slow progress
- Milestone target:
- None
- Started by
- Jeff Johnson
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Adding macro templates pre- and post- just like build scriptlets permits envvars to be set from macros. That should suffice.
Embedded interpreters have their own speshul pains. Instead of envvar scraping: using the interpreter symbol table persistently is a better approach.
The $1/$2 arguments need to be phased out so that general scripts can be run. See the SuSE patch to ignore $1/$2 in /sbin/ldconfig for the rationale for eliminating $1/$2 as now. Also the multilib proposal for adding $3/$4 ickiness.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
