Make individual Lua scriptlets execute in their own enviroments
Bug #637049 reported by
Jeff Johnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| RPM |
New
|
Undecided
|
Unassigned | ||
| CentOS |
New
|
Unknown
|
|||
Bug Description
tracker
| tags: | added: lua rpm.org scriptlet |
| Changed in centos: | |
| status: | Unknown → New |
Revision history for this message
| Jeff Johnson (n3npq) wrote | #1 |
To post a comment you must log in.
The LUA embedding deliberately chose to use a global
interpreter so that the LUA environment is persistent.
The goal is/was to be able to send messages between
various embedded LUA scriptlets to coordinate
complex multi-stage installations.
Meanwhile there's nothing stopping adding a flag
to create an isolated server instance. In fact all
embedded interpreters in RPM can be instantiated
either once globally persistently, or as a single instance.
Note that various embeddings -- python/ruby -- can only
be invoked once globally. But lua/tcl/perl embeddings
can be either globally persistent or lightweight and isolated,
depending on a flag passed when the interpreter is instantiated.