[squeak-dev] [Ann] New build of 3.10.2-build

http://ftp.squeak.org/3.11/3.10.2-build/
http://ftp.squeak.org/3.11/3.10.2-build/090213-0428-Squeak3.10.2-build-beta.zip

All being well I shall be using this image as the basis for a new
project this week.

best regards

Keith


=
Notes:

This has the new updated image #cleanUp method set following yesterday's
discussion.
The repository with saved packages is squeaksource/310build
The unloads listed in the readme will not work until the next build.

I renamed 3.10.2bc to 3.10.2-build in order to try and lessen confusion
over the naming.

i.e. The naming convention works like so:

3.10.2-build is an image derived from 3.10.2 for building purposes.
3.11-build is an image derived from 3.11 for building purposes.
3.11-test is an image derived from 3.11 for testing purposes etc etc

On Fri, Feb 13, 2009 at 5:15 PM, Keith Hodges <[hidden email]> wrote:
> http://ftp.squeak.org/3.11/3.10.2-build/
> http://ftp.squeak.org/3.11/3.10.2-build/090213-0428-Squeak3.10.2-build-beta.zip
>
> All being well I shall be using this image as the basis for a new
> project this week.

What about a squeak-dev based on it? Are people interested?

--
Damien Cassou
http://damiencassou.seasidehosting.st

could be nice to see squeak-web ;]

Damien Cassou wrote: I was going to mention that, am I right in saying that all you have to
do is...

Installer sake install: 'Squeak-dev image'.

Ken Brown tried it last night, and it seemed to work ok.

Keith


btw: I see that you are manually applying some fixes at the
end/beginning. I discovered how you can load files (fix changesets) from
mantis in universes. Simply put the mantis url to the changeset in the
package definition url and add ?ext=.cs to the end so that Universes
sees a file extension.

On Fri, Feb 13, 2009 at 6:12 PM, Keith Hodges <[hidden email]> wrote:
> I was going to mention that, am I right in saying that all you have to
> do is...
>
> Installer sake install: 'Squeak-dev image'.


You are right. What I propose is to make 3.10.2-build a base image for
the future dev-images. That means a new dev image each month based on
your version.

> Ken Brown tried it last night, and it seemed to work ok.
>
> btw: I see that you are manually applying some fixes at the
> end/beginning.


?? Where did you see that? That's not true, I'm not applying any fix
to the base images. I'm only installing packages.


--
Damien Cassou
http://damiencassou.seasidehosting.st

Damien Cassou wrote: definitely the way forward.

In your building page:

sake
  answer: '.*username.*' with: 'admin';
  answer: '.*password.*' with: 'seaside';
  answer: 'Would you like.*' with: true;
  answer: '.*port number.*' with: '8080';
  answer: '.*is .* running.*' with: true;
  answer: '.*name of your Pier kernel.*' with: 'Pier';
  answer: '.*entry point.*' with: 'pier';
  answer: '.*Application' with: true.

Sake (should) already include these. The planned policy is that installs
should be non interactive by default.
>
> ?? Where did you see that? That's not true, I'm not applying any fix
> to the base images. I'm only installing packages.
>  
Ken mentioned it, nm

Keith

At 7:44 PM -0800 2/13/09, [hidden email] apparently wrote:
My bad, I mentioned to Keith that the readme in the dev images said:

Installer mantis ensureFix: '6466 LazyListMorph-listChanged'.
Installer mantis ensureFix: '4874 Split and join'.
Installer mantis ensureFix: '7007 toggle break'.

and I missed reading the comment saying "These are fixes which you can selectively apply to the base 3.10 image"

One of them was already in the image but it may have come from something else I had done.
I incorrectly assumed the fixes were already applied.

By the way, where did the tasks come from for Installer sake install: 'Squeak-dev image'.?
Damien, are they something you came up with? Not sure what all it does but it ends up looking kinda like a dev image after doing a bunch of dev image building type things. I was trying things out testing the overall process without really getting into detail about what was being done.

Ken G. Brown

>--
>Damien Cassou
>http://damiencassou.seasidehosting.st

> By the way, where did the tasks come from for Installer sake install: 'Squeak-dev image'.?
>  
The tasks are defined in www.squeaksource.com/Packages in the
Packages-Library packages.

Within that package there is a class PackagesDevU whose instance side
methods provide package definition metadata that has been
obtained/gernerated from Universes. The class PackagesDev inherits and
overrides the PackagesDevU with any further information.

Keith

What I really meant was, how close it this to what Damien has been doing?
Damien says:
<http://damiencassou.seasidehosting.st/Smalltalk/squeak-dev/Building>

Who created the list of things that gets done when you doit Installer sake install: 'Squeak-dev image'.?

Powerful stuff in any case.

Thx,
Ken G. Brown

On Fri, Feb 13, 2009 at 8:55 PM, Keith Hodges <[hidden email]> wrote:
I don't think it's the case yet because the package declarations come
from Universe which does not support that. As soon as I move
completely to Sake, I will remove them.

--
Damien Cassou
http://damiencassou.seasidehosting.st

On Sat, Feb 14, 2009 at 1:24 PM, Ken G. Brown <[hidden email]> wrote:
> Who created the list of things that gets done when you doit Installer sake install: 'Squeak-dev image'.?

'Squeak-dev image' is a universe package which depends on 'Squeak-dev
packages' and installs ImageForDevelopers from SqueakSource.

ImageForDevelopers is a small project which sets preferences and
writes documentation in the ScriptManager. It also closes unnecessary
windows, cleans the memory...

'Squeak-dev packages' is a meta-package which does not install
anything but depends on a lot of other packages like eCompletion,
Shout, OB...

--
Damien Cassou
http://damiencassou.seasidehosting.st

Damien Cassou wrote: Ah, but the universe definitions are generated into PackagesDevU. This
is overridden in PackagesDev with the following:

Seaside

   super Seaside.
    self info mcName: 'Seaside2'.
    self answer: '*config*' with: 'seaside';
        answer: '*password*' with: 'admin'.
       
 PierSeaside

    super PierSeaside.
 
    self answer: '*Would*' with: true;
        answer: '*Pier kernel*' with: 'Pier';
        answer: '*entry point*' with: 'pier';
        answer: '*Pier-Application*' with: true;
        yourself

cheers

Keith

On Mon, Feb 16, 2009 at 1:19 PM, Keith Hodges <[hidden email]> wrote:
> Ah, but the universe definitions are generated into PackagesDevU. This
> is overridden in PackagesDev with the following:

Ok, thank you.

--
Damien Cassou
http://damiencassou.seasidehosting.st