Open PalumboN opened 5 months ago
Hi @PalumboN
Indeed, Pharo Launcher has a strong requirement to manage images: it should be contained in a folder that has the same name as the image file and the image file is contained in this folder.
Pharo Launcher is not ready for the new image format. It has to be done (but not yet on the roadmap).
Current Pharo Launcher will fail to read the image version number, find the metadata, etc.
Also, it is already doable to run an image stored anywhere on the file system. pharo-launcher image launch aPath/to/myimage.image
but it will also fail to read metadata, image version, ...
Hi @demarey !
Oookkk, I'll try to help with the new image format support in the next sprint 😄
We can also talk about running an image stored anywhere. My case of use is simple because I download the image using the launcher, and then I need to move it to other folder because of a benchmark framework... But the structure of the folder is the default one.
Thank you!!
To use the Permanent Space (a.k.a Permi), the new feature of the Garbage Collection, we changed the image format. It seems to cause problems about how the laucher finds the images.
Reproduce it I created a new image and list them:
Then I migrated
test-permi
to an image with permanent space following these instructions.Now the image is not listed anymore.
But the image is still in the same place:
And I can not run others commands neither 😢
Probably it happens because the new image format is a folder, instead of a single file:
Expected behavior
I would like two (kind of) different things:
The launcher should recognize the new image format (folder).
Anyway, I would like to run commands with local images that are not listed by
pl
(they are in random folders). Sending the path instead of justexistingImageName
. For example:pl image launch ./Documents/Pharo/images/test-permi/test-permi.image
Version information:
iOS 12.2.1
3.1.1-476-g723df186