I'm pretty sure the responsibility falls to the loader. I'm not too familiar with it but if I wanted to be I would probably start tracing from McVersionLoader. Do your pool references end up being valid? That is the most important but I agree it would be an annoyance to see those messages in the Transcript. On Mon, Dec 8, 2014 at 7:24 AM, Craig Latta <craig@netjam.org> wrote:
Hoi--
I'm attempting to create a Monticello package which provides a shared pool (as a subclass of SharedPool) and methods which use its variables. On installation, does Monticello try to ensure that a pool is installed before methods which use it? When I install the package in a fresh system, I get messages on the Transcript complaining that shared variables are undefined.
Is there some way one fiddles with the writing process, or with the package after it is written, to avoid ordering problems?
thanks!
-C
-- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)