Yes I like it too.
This is why I want to invest on it.
On Sep 30, 2008, at 4:27 AM, Igor Stasenko wrote:
I like the Installer.
Its a simple tool to break your work onto multiple stages/packages.
It is very useful for making automatic builds.
No manual image hacking - instead you have to fix
Keith
could you make sure that the tests can run when we load the installer
and its tests?
I do not know what is the classcloner...
Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
So fixes are not integrated into the image anymore and the report
then
closed?
When a release image is released the fixes are integrated into the
image
as normal, and can be closed or marked fixed.
Release image? that means, you will not close *any* bug-report until
you release
3.11?
Stéphane Ducasse wrote:
We will see at the end what was the better Idea ;-)
Good challenge :)
I will integrate a bit more etoys now.
Stef
Not a challenge I am taking up, I have a ball joint to replace on my
car, and no time to input into this at the moment.
Keith
Release image? that means, you will not close *any* bug-report until
you release
3.11? Wow. But you sure close at least duplicated bug-reports?
Wow what? The release will know which bug fixes are included and provide
a list of fixes which can be closed, when the release is actually ready
and
I like the Installer.
Its a simple tool to break your work onto multiple stages/packages.
It is very useful for making automatic builds.
No manual image hacking - instead you have to fix the scripts or packages.
This will guarantee that every time you will load the same code as
before, w/o losing
Damien Cassou writes:
Polymorph is going to be included in all Pharo images so you don't
have to worry. RB as been in all my images from the beginning and will
continue to be. I think I will stop generating web images for Pharo
because we want only one image for Pharo. I will try to find a
On Sun, Sep 28, 2008 at 12:36 PM, [EMAIL PROTECTED] wrote:
Damien Cassou writes:
Polymorph is going to be included in all Pharo images so you don't
have to worry. RB as been in all my images from the beginning and will
continue to be. I think I will stop generating web images for Pharo
100% agree. This is why I'm saying that we want to integrate extensions
or reject them.
If it doesn't meet those criteria, I don't consider it safe to even
experiment with.
However, if the base system doesnt support loading and unloading of
things in the first place, its a bit unfair to
On 28.09.2008, at 19:01, Keith Hodges wrote:
Now, the code may work perfectly fine, and Keith's done a lot of
work, but
it's just not community friendly code. A package should have a clear
responsibility, few dependencies, not too many extensions, no
overrides if
at all possible, and
considering that mantis now has 1000 open entries...
Marcus
??
The difference being, that we dont create a mantis entry so that it can
languish unused. We use mantis as a vessel for holding snippets of code
and collecting feedback.
Installer collects a list of fixes applied, and
Marcus Denker wrote:
On 28.09.2008, at 22:16, Keith Hodges wrote:
considering that mantis now has 1000 open entries...
Marcus
??
The difference being, that we dont create a mantis entry so that it can
languish unused. We use mantis as a vessel for holding snippets of code
and
Damien, Stef,
I _think_ what I would want for a starting point is something like Damien's web
image, followed by a script that gets the latest of a few things, specific
versions of others, and then loads a bunch of .cs or other files for my code.
Damien, I suspect you put a lot of work into
On Fri, Sep 26, 2008 at 8:38 AM, Lukas Renggli
[EMAIL PROTECTED] wrote:
One problem I see with Sake/Packages is that these tools depend on a
lot of other packages, that I don't necessarily want to
have loaded in
my images: Logging, Rio, Installer, Sake, Packages ...
I guess one
My objection, the big ball of mud called Kernel-Extensions and the
liberal
use of overrides, which I think are evil. I like using packages
that do
their best to only use extensions and don't just go around the
system willy
nilly monkey patching everything. I don't trust packages with
15 matches
Mail list logo
