In Pharo 2.0, we could enforce the image not to look for sources and changes file at the startup with:

I could not found these selectors anymore in my Pharo 3.0 image.

Clement mentioned to me a while ago that it was due to the change of compiler (Opal) and it might not be safe to remove these files (if I remember correctly). So, my question:

1/ Can I remove these two files safely from my production image?

2/ If the answer to 1/ is yes, how can I tell my image not to look for these files at image startup?

tx,

Usman