Yeah, I'm somewhat of a Pharo hacker and the workflow is pretty similar to any other software: Start with a base image, create a package, add code to the package, use git (via Iceberg) to save diffs for a particular package off for distribution. It's analogous to hacking on an operating system image in a container: keep your code and the system separate (via the "packages" abstraction in a Pharo image, or via the filesystem in an OCI container image) and you will be fine. The "Baseline" concept is a bit opaque (and weirdly named IMO, but a lot of the Pharo community is European, and especially French, so presumably it makes more sense in that context) but is a form of dependency management that works OK, though it would be nice to have a more Linux-distro type experience for installing packages.
Comments
Yeah, I'm somewhat of a Pharo hacker and the workflow is pretty similar to any other software: Start with a base image, create a package, add code to the package, use git (via Iceberg) to save diffs for a particular package off for distribution. It's analogous to hacking on an operating system image in a container: keep your code and the system separate (via the "packages" abstraction in a Pharo image, or via the filesystem in an OCI container image) and you will be fine. The "Baseline" concept is a bit opaque (and weirdly named IMO, but a lot of the Pharo community is European, and especially French, so presumably it makes more sense in that context) but is a form of dependency management that works OK, though it would be nice to have a more Linux-distro type experience for installing packages.