Re: [Pharo-users] Problem learning about Magritte
Esteban wrote:
I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long.
I strongly encourage the use of ci images. And of course you should add your own, once you've decided what packages you need. The main advantage is that it provides feedback to the core pharo development on changes. Stephan
2014-05-12 20:47 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
Esteban wrote:
I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long.
I strongly encourage the use of ci images. And of course you should add your own, once you've decided what packages you need. The main advantage is that it provides feedback to the core pharo development on changes.
2014-05-12 20:47 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
Esteban wrote:
I don't like this "faster way" of prebuilt images. Makes me think of seeds for forked branches. Unless something is wrong with the package system, I would encourage its use, even if it takes long.
I strongly encourage the use of ci images. And of course you should add your own, once you've decided what packages you need. The main advantage is that it provides feedback to the core pharo development on changes.
I'm totally in about CI images for testing purposes, but not for distribution. Maybe it's a matter of personal taste. Esteban A. Maringolo ps: sorry for the off topic
participants (2)
-
Esteban A. Maringolo -
Stephan Eggermont