@User in my experience in commercial VLSI companies, porting a project on a different machine/filesystem (for example on Cadence) also involved changing configuration files to tell the tool where things are located (cds.lib ad similar) This can be abstracted using shell env variables (so less changes required in xschemrc) if we have a clear convention on what is used for what, variables can be used easily by xschem/xschemrc as well. Let me know if some different approach is needed and additions are needed, to make integration with the skywater ecosystem consistent and hassle-free.