Hi Brad, Envy is a package manager. It does not define the minimal kernel you need to install packages needed for your application. The goal of a bootstrap is to set up an environment from a know state. In the same time, this exercise forces us to define the minimal kernel needed to run Pharo (because you do not want to bootstrap the full system). Currently, we miss both the minimal kernel and a bootstrapped image of Pharo.
Le 20 janv. 2016 à 20:17, Brad Selfridge a écrit : > Has anyone looked at the VASmalltalk Envy Packager. It let's one decide > whether you want to package a headless or UI image. It then allows one to > define packaging instructions, that are saved with the new application), > that get fed into the packager. The instructions define prerequisite apps, > un-referenced methods, etc. When one defines a new application (package), > one can define prerequisite applications that have to be installed before > the current application is installed. This prerequisite chain is used in > loading the application from Envy and in packaging. Seems to work fairly > well. Doesn't take too long to package an app and give the developer pretty > fine control over the packaging and loading process. > > > > ----- > Brad Selfridge > -- > View this message in context: > http://forum.world.st/ANN-Pharo-bootstrap-tp4872633p4872989.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
smime.p7s
Description: S/MIME cryptographic signature
