I'm rather curious now about how you manage Pharo. I took a look
at http://code.google.com/p/pharo/wiki/HowToContribute and
wondered what happens after that. I now imagine it involves
ScriptBuilder building the update, and then something uploading
it. What is the mechanism?
ok so the scriptloader is our friend since early days of 3.9.
It is basically a set of functionality which can load a description of
packages.
two methods are generated
- scriptXXX
contains the list of packages
- update100XX
contains now a description
code to load the list
cleanups
We did not use mcm because it did not work for us at that time.
We have sometimes the need to load sequentially packages and not all
at the same time.
How is Pharo tested? is it regularly tested by someone using
TestRunner, or something fancier?
For now there is not automated regression mechahnism
Laurent Laffont and Alexandre Bergel are working on a test server.
What are all the auto-generated methods in ScriptLoader for?
to be able to go back in the past. we can always know all the packages
of a given image.
Even if sometimes we cannot take 3.9readyForPharo and simply press the
button
to reproduce the image. This is due that some changes should be done
via cs and produces
dirty packages that in the past could not be reloaded. Like MVC having
broken initialize method
and also due to the fact that atomic loading was not working (we will
get there when we will
finally use MC1.6 - but you know that we will not do it at the price
of bringing code we do
not like, but we are making progress on that :).
How do you typically trace a bug from image to problem package
to update to issue?
Manually. It sucks!
I'm interested because keith and I are building a build server
that is able to build images, build packages, load packages, run
tests, build VM's and such, all automated and with an easy
interface. So far, we have the easy interface (Installer), but
are still working on making it do more.
I know, I discussed about with keith long time ago and I like
what he is doing. Now again we will review and give feedback.
Bob is important, Installer too.
So I'm interested in learning how it works here, so that we can
at least end up with something as good as this
Scriptloader is not good, it is what we made for making progress.
As soon as we have something better we throw it away. Believe
me this mainly my code :)
--
Matthew Fulmer -- http://mtfulmer.wordpress.com/
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
