Closed ghost closed 3 years ago
This messages are annoying because they require confirmation. In a scenario where one wants to load packages at image boot via script, the script gets stuck awaiting user click. Attach picture of the message.
nono, all bad, we slipped on a banana. I mistook OSProcess with OSProcesses. Running either
Feature require: 'OSProcess'.
or
vmDir _ DirectoryEntry smalltalkImageDirectory .
pathStr1 _ vmDir parent pathName, '/OSProcess/OSProcess.pck.st'.
file1 _ FileSystemEntry withPathName: pathStr1.
CodePackageFile installPackage: file1.
works flawlessly.
On the other side this rises another point. If the message was more informative we would not have fallen so badly ;)
IMO, this can be closed.
Yep, I agree. Thanks Juan!
The title describes the problem. This is a duplicate of https://todo.sr.ht/~cy-de-fect/HaverOnCuis/10 and resulted from this E-Mail report: https://todo.sr.ht/~cy-de-fect/HaverOnCuis/10
Hi Nicola,
I am doing something similar to transform a Cuis-image into a Haver-image, but I am using Feature:
https://hg.sr.ht/~cy-de-fect/HaverOnCuis/browse/haver/Haverize.pck.st?rev=tip#L27
I don't get any unwanted confirmation dialogs.
Are you referring to the message displayed in the attached screen-shot. The message is rather silly. Please use Feature>>#require: with a FileSystemEntry instance as an argument.
(Nevertheless we should fix that silly message)
Best Regards and HTH,
Gerald
On 7/30/21 12:18 PM, Nicola Mingotti via Cuis-dev wrote: