Summary
indirectly loaded extension to statically linked extension-modules may still be loaded dynamically
Metadata
- Id: b98310e68bbdb5f5ebcb6d299d593fcf38ac9392
- Trac id: 420
- Type: defect
- Reporter: felix
- Owner: felix
- Cc:
- Status: closed
- Component: core libraries
- Estimated difficulty:
- Resolution: wontfix
- Priority: major
- Milestone: 4.9.0
- Version: 4.6.x
- Changetime: 2012-09-24 21:47:48 UTC
- Created: 2010-10-29 15:45:57 UTC
- Keywords:
Description
It might be helpful to internally mark explicitly statically linked extension in an executable (`-static-extension`) as "pre-loaded", for example by adding them to `##sys#loaded-extensions` before loading `require`'d extensions.
Changes and comments
[2010-11-10 12:43:48 UTC] felix changed status from new to closed
[2010-11-10 12:43:48 UTC] felix set resolution to wontfix
[2010-11-10 12:43:48 UTC] felix wrote:
At T-DOSE we have come to the conclusion that any effort for statically linkable eggs will be silently dropped. It is too much of a hassle to get this working, the user interface is awkward, and egg-authors don't test static linking in most cases. Since it is easier to just use `-deploy` if self-contained binaries are desired this feature will be phased out.
[2011-06-01 09:00:41 UTC] felix changed milestone from 4.7.0 to 4.8.0
[2011-06-01 09:00:41 UTC] felix wrote:
Milestone 4.7.0 deleted
[2012-09-24 21:47:48 UTC] felix changed milestone from 4.8.0 to 4.9.0
[2012-09-24 21:47:48 UTC] felix wrote:
Milestone 4.8.0 deleted