Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#73 closed defect (fixed)

building an extension will prefer already installed eggs over currently built ones

Reported by: felix winkelmann Owned by:
Priority: major Milestone:
Component: compiler Version: 4.1.x
Keywords: Cc:
Estimated difficulty:

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.

Change History (2)

comment:1 Changed 10 years ago by felix winkelmann

Resolution: fixed
Status: newclosed

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 ...).

comment:2 Changed 10 years ago by (none)

Milestone: 4.3.0

Milestone 4.3.0 deleted

Note: See TracTickets for help on using tickets.