Cool, thanks! My script was getting too complicated, so I made it into a class with a MetaC config, and the script is now just a Gofer load. This has the additional benefit that the start up scripts for the Pharo loader never change (they're just Gofer loads) and so avoid the caching problems that can otherwise arise.
Yes this is the right way to manage scripts: turn them into classes :)
Torsten Bergmann wrote"Set password for Squeaksource" (MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [((each locationWithTrailingSlash includesSubstring: 'www.squeaksource.com') or: [each locationWithTrailingSlash includesSubstring: 'http://ss3.gemstone.com/ss/'])] ]) do: [:each | each user: 'squeaksourceuser'; password: 'secretsqueaksourcepassword']. ...I do something like this too. The shortcoming is that newly created repos are not authenticated. This should be in core built into the repo objects. I guess that's what the KeyChain stuff is about? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tip-Image-init-scripts-when-working-with-PharoLauncher-tp4770062p4770135.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
