Hi,
I think I know how this *does* work, but I want to verify that this is how it *should* work. Here's the scenario. A module being worked on in two different environments. Now in Environment A, the module is updated, and a new compiled ospace is transported to Environment B. Environment B has the source code from before. Will the old source in Environment B now cause an overwrite of the newly transported version of the module, or will the source on Environment B be updated to reflect the changes done in Environment A?
My theory is that CSIDE will go one way or the other depending on which has an older timestamp, but is this universally so (ie is this as designed). Anecdotally, I've seen old source clobber changes to a new version of a module as well as the new module being converted properly to source, but I'm not sure what guarantees the direction of flow.
I know I *could* copy the source from one environment to the other and affect a rebuild, but ideally, I'd like the compiled module to be the final source of truth for the purposes of distribution.
I may send updates to this as I attempt this very thing.
-Hugh
