Summary
building an extension will prefer already installed eggs over currently built ones
Metadata
- Id: 0b3517655ff5e696d4e6f445423ab58ac2b8f427
- Trac id: 73
- Type: defect
- Reporter: felix
- Owner:
- Cc:
- Status: closed
- Component: compiler
- Estimated difficulty:
- Resolution: fixed
- Priority: major
- Milestone:
- Version: 4.1.x
- Changetime: 2010-03-11 10:33:12 UTC
- Created: 2009-09-04 15:48:04 UTC
- Keywords:
Description
Building an extension may need to load extensions/.so's that have just been produced by the current installation process, but require'ing extensions will always look in the repository first (and possibly load an obsolete version, if the extension has been installed at an earlier point).
We should provide an option (csc + chicken) that forces the search/load order to look in the current directory first. Note that the correct order for normal use should stay repo-first, then current directory, or random files in the current directory may break applications. `chicken-install` should invoke csc with the extra option.
Changes and comments
[2009-09-09 10:10:32 UTC] felix changed status from new to closed
[2009-09-09 10:10:32 UTC] felix set resolution to fixed
[2009-09-09 10:10:32 UTC] felix wrote:
Has been fixed by introducing the `-setup-mode` option, which places the current path before the repository path for locating extensions. `chicken-install` handles this transparently as long as setup scripts use `(run (csc ...))` or `(compile ...)`.