19:24:16shinmeraRight now I'm dealing with this problem: when you create a component it iterates over its supported operations, and creates effects that it can create in a database.
19:24:26shinmeraThis is fine, and it needs to do this for planning to work at all.
19:24:39shinmeraBut: now consider something like compile-file, which produces a fasl artefact as output.
19:25:07shinmerain order to create this artefact, it needs to create a pseudo path
19:25:22shinmerain order to do that though it needs to know the compiler that's going to be used
19:25:36shinmeraand it can't know that until the plan is actually being computed
21:00:55ColleenShinmera: represent the path as #<fasl-of #P"foo.lisp"> for the purposes of planning, then convert it to "real" fasl path once you know what compiler is used?
21:00:55SAL9000Shinmera: represent the path as #<fasl-of #P"foo.lisp"> for the purposes of planning, then convert it to "real" fasl path once you know what compiler is used?
23:22:50selwynwondering how much trial has changed since i last hacked trial-vr