- assigned_to: nobody --> marcoxa
Hi,
We're trying to use mk:defsystem for our system management. However, the functionality we require is relatively non-standard, and I would like to make a case for supporting it in defsystem.
We do not have a central repository. Fixing a central repository for a large development effort is inconvenient to say the least. Instead, if system A depends on system B, we explicitly give a path for system B's system definition file while defining system A.
(defsystem A
...other args...
:depends-on ((B <file containing system B's definition>)))
Unfortunately, defsystem appears to distinguish between the cases where one has a central repository and where one does not. When it comes time to operate on dependencies, defsystem hands the loading of B to new-require, which believing that the system is loaded ignores the fact that the system definition for B has been updated and the compiled files are now stale. I would instead have defsystem check for out of date system definition files, and regardless of whether the system was reloaded, have defsystem operate on the subordinate system B when it is asked to operate on the primary system A. I find the current behavior of defsystem rather damaged, and would like to know if you (the developers) have considered fixing this.
Thanks,
Sunil