[Pharo-project] Script passing and StartupPreferences
It seems that (in 1.4, not sure about 2.0) if an image is launched with a script (e.g. "cogvm my.image my.st"), StartupPreferences are never run. Is that what's intended? I just realized, for instance, that all my images that were built by my Jenkins server (which pass a script as above) aren't using my shared cache (which is set in the preferences) and are downloading from http every time, yuck... Cheers, Sean -- View this message in context: http://forum.world.st/Script-passing-and-StartupPreferences-tp4643406.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Sean P. DeNigris wrote
It seems that (in 1.4, not sure about 2.0) if an image is launched with a script (e.g. "cogvm my.image my.st"), StartupPreferences are never run. Is that what's intended?
After experimenting a bit, it seems that preferences are loaded after script arguments are handled, so if the script ends in #snapshot:andQuit:, the prefs never get loaded. I'm thinking the prefs should be loaded before any scripts. For example, I want my shared cache to be set as the package cache before any load scripts are run. What do y'all think? Cheers, Sean -- View this message in context: http://forum.world.st/Script-passing-and-StartupPreferences-tp4643406p464370... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
+1, preferences should be loaded before any laod scripts. On 09/08/12 12:20, Sean P. DeNigris wrote:
Sean P. DeNigris wrote
It seems that (in 1.4, not sure about 2.0) if an image is launched with a script (e.g. "cogvm my.image my.st"), StartupPreferences are never run. Is that what's intended?
After experimenting a bit, it seems that preferences are loaded after script arguments are handled, so if the script ends in #snapshot:andQuit:, the prefs never get loaded.
I'm thinking the prefs should be loaded before any scripts. For example, I want my shared cache to be set as the package cache before any load scripts are run.
What do y'all think?
Cheers, Sean
On 2012-08-09, at 22:54, Francois Stephany <tulipe.moutarde@gmail.com> wrote:
+1, preferences should be loaded before any laod scripts.
indeed, so we have to change the order in the startup list...
On 09/08/12 12:20, Sean P. DeNigris wrote:
Sean P. DeNigris wrote
It seems that (in 1.4, not sure about 2.0) if an image is launched with a script (e.g. "cogvm my.image my.st"), StartupPreferences are never run. Is that what's intended?
After experimenting a bit, it seems that preferences are loaded after script arguments are handled, so if the script ends in #snapshot:andQuit:, the prefs never get loaded.
I'm thinking the prefs should be loaded before any scripts. For example, I want my shared cache to be set as the package cache before any load scripts are run.
What do y'all think?
participants (3)
-
Camillo Bruni -
Francois Stephany -
Sean P. DeNigris