[squeak-dev] Error when installing OSProcess from SqueakMap
bernhard at pieber.com
Sun Apr 14 18:16:50 UTC 2019
Thanks for the help.That is much easier than installing from SqueakMap anyway. I had thought about installing OSProcess and CommandShell from SqueakSource. However, I was not sure because of the other packages OSProcess-Base, OSProcess-Tests which were recently updated as well. It seems they are not needed because they are not loaded with your loading instructions?
Thanks for your work on Squeak!
> Am 13.04.2019 um 19:02 schrieb David T. Lewis <lewis at mail.msen.com>:
> Wow, that's a new one on me.
> I don't know what the issue is with the SqueakMap loading, but the
> 'head' scripts for OSProcess and CommandShell do this:
> MCMcmUpdater updateFromRepository: 'http://www.squeaksource.com/OSProcess' .
> MCMcmUpdater updateFromRepository: 'http://www.squeaksource.com/CommandShell'.
> These work fine when evaluated outside of SqueakMap, so I would suggest
> doing that for the time being. I don't know what the issue when loading
> from the SqueakMap loader, sorry.
> On Sat, Apr 13, 2019 at 05:20:07PM +0200, Bernhard Pieber wrote:
>> I tried installing OSProcess in a fully updated trunk image according to the installation instructions on http://wiki.squeak.org/squeak/708:
>> "Use the latest version of OSProcess and CommandShell, and load both of them. Load both from SqueakMap. Please use the head (latest version) and ignore any Squeak version tags or warnings.
>> OSProcess and CommandShell are Squeak version independent, but there is no way to say that with SqueakMap."
>> Here are the steps I took:
>> 1. I selected Apps > SqueakMap catalog.
>> 2. I clicked the Update button.
>> 3. I deselected "New safely-available packages" from the bottom-left list's context menu. (It took me quite a while to figure that out.)
>> 4. I expanded OSProcess in the top-left list and clicked on (head)
>> 5. I clicked the Install button.
>> 6. The following error appears:
>> "Error occurred during install:
>> Receiver and argument in different branches
>> Would you like to open a debugger?" (See the attached debug log for details.)
>> The error seems to break SqueakMap. From now on it always opens when I try to open SqueakMap.
>> - Bernhard
More information about the Squeak-dev