Problem loading Metacello [WAS] The road to 1.0

Hi Dale. I changed the subject as I think I found a problem.

Gofer new
    gemsource: 'metacello';
    package: 'ConfigurationOfMetacello';
    load.

This download only the ConfigurationOfMetacello. Perfect.

Now, I just evaluate this:

 ((Smalltalk at: #ConfigurationOfMetacello) project version: '1.0-beta.25')

And that, downloads Metacello!!!  Why ?? If I didn't do any load of the version ? is that correct ? I would expect that code not to load anything about the project until I said "load". Maybe I am wrong...just wanted to be sure.

So, to load Metacello is not needed the load ?

Even more, aftere valuating that, I print

ConfigurationOfMetacello project currentVersion

and I get  ~1.0-beta.24.1 [ConfigurationOfMetacello]

Cheers

Mariano

To unsubscribe from this group, send email to metacello+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.

Mariano,

If Metacello hasn't been bootstrapped yet, sending the #project message to ConfigurationOfMetacello will bootstrap the latest version of Metacello (in this case 1.0-beta.24.1).

You still need to do the load to get 1.0-beta.25, because it is still under #development.

Dale
----- "Mariano Martinez Peck" <[hidden email]> wrote:

| Hi Dale. I changed the subject as I think I found a problem.
|
| Gofer new
|     gemsource: 'metacello';
|     package: 'ConfigurationOfMetacello';
|     load.
|
| This download only the ConfigurationOfMetacello. Perfect.
|
| Now, I just evaluate this:
|
|  ((Smalltalk at: #ConfigurationOfMetacello) project version:
| '1.0-beta.25')
|
| And that, downloads Metacello!!!  Why ?? If I didn't do any load of
| the
| version ? is that correct ? I would expect that code not to load
| anything
| about the project until I said "load". Maybe I am wrong...just wanted
| to be
| sure.
|
| So, to load Metacello is not needed the load ?
|
| Even more, aftere valuating that, I print
|
| ConfigurationOfMetacello project currentVersion
|
| and I get  ~1.0-beta.24.1 [ConfigurationOfMetacello]
|
| Cheers
|
| Mariano
|
|
|
|
| ---------- Forwarded message ----------
| From: Dale Henrichs <[hidden email]>
| Date: Sat, Mar 20, 2010 at 4:45 PM
| Subject: Re: [Metacello] The road to 1.0
| To: [hidden email]
|
|
| Woops, I hadn't pushed a recent ConfigurationOfMetacello to
| MetacelloRepository ... try again ..
|
| Dale
| ----- "Mariano Martinez Peck" <[hidden email]> wrote:
|
| | On Sat, Mar 20, 2010 at 2:12 AM, Dale Henrichs
| | <[hidden email]>wrote:
| |
| | > Mariano,
| | >
| | > Try using Metacello 1.0-beta.25 ... today I've just run through
| | loading
| | > latest for Seaside3.0/Seaside2.8/Moose so I don't anticipate to
| many
| | changes
| | > and if you run into other troubles now would be a good time. So
| I've
| | tried
| | > the following to good effect (once 1.0-beta.25 is loaded
| noisily):
| | >
| | >  | version |
| | >  version := ConfigurationOfMetacello project version:
| | '1.0-beta.25'.
| | >  version silently: true.
| | >  version load: 'ALL'.
| | >
| |
| | Here I have a problem. Evaluating this:
| |
| |
| | Gofer new
| |     squeaksource: 'MetacelloRepository';
| |     package: 'ConfigurationOfMetacello';
| |     load.
| |
| |
| |  version := ((Smalltalk at: #ConfigurationOfMetacello) project
| | version:
| | '1.0-beta.25').
| |  version silently: true.
| |
| | Gives me a DNU with silently:
| |
| | After that, I checked evaluating:
| |
| | ConfigurationOfMetacello project currentVersion
| |
| | and prints   ~1.0-beta.24.1 [ConfigurationOfMetacello]
| |
| | Instead of beta.25. Of course, in 24.1 there was no silently, and
| | thus, the
| | DNU.
| |
| | Any idae how can I fix this ?  do you know when you are going to
| | release
| | beta25 ?
| |
| | As I want to release PharoRC3 SOON I want so see if I rollback my
| | change
| | (not a big deal at all) or if I wait.
| |
| | Thanks a lot Dale.
| |
| | Mariano
| |
| |
| |
| | >
| | > and it should work if you with ConfigurationOfPharo...
| | >
| | > Dale
| | > ----- "Mariano Martinez Peck" <[hidden email]> wrote:
| | >
| | > | Hi Dale. I am experimenting again the problem with the progress
| | bar.
| | > | Do you
| | > | remember that when loading ImageForDevelopers trough Metacello
| I
| | have
| | > | this
| | > | problem as in the post load of that package I reset the
| progress
| | bar
| | > | ?
| | > |
| | > | Ok...today I put ImageForDevelopers again inside the Metacello
| | > | configuartion, to try if it was working but I am still having
| | > | problems. I
| | > | attach PharoDebug.log
| | > |
| | > | To reproduce you have to take a PharoCore10515. If you try to
| | load
| | > | ConfigurationOfPharo in that image, in this way, it works ok:
| | > |
| | > | Gofer new
| | > |     squeaksource: 'MetacelloRepository';
| | > |     package: 'ConfigurationOfPharo';
| | > |     load.
| | > |
| | > | ((Smalltalk at: #ConfigurationOfPharo) project version:
| | > | '1.0-rc3.10515')
| | > | load.
| | > |
| | > | The problem is that I run the core image from command line
| | sending
| | > | that text
| | > | in a file (as parameter). Only there I have this problem :(
| | > |
| | > | Thanks
| | > |
| | > | Mariano
| | > |
| | > | On Tue, Feb 23, 2010 at 11:10 AM, Mariano Martinez Peck <
| | > | [hidden email]> wrote:
| | > |
| | > | > For the progressBar, I would let something by default as it
| is
| | in
| | > | > MetacelloPlatform >> do: aBlock displaying: aString
| | > | >
| | > | > The MetacelloPharoPlatform >> do: aBlock displaying: aString
| | > | >
| | > | > I would like to have it only with Metacello-OB as Dale
| | suggested.
| | > | >
| | > | > Regarding the prefetchLoad:    cannot we use the project
| | loadType:
| | > | #linear.
| | > | >
| | > | > So that we can do project loadType: #preFetch.
| | > | >
| | > | > ?
| | > | >
| | > | > or the type is something different that I a confusing and
| mixing
| | ?
| | > | >
| | > | > Cheers
| | > | >
| | > | > Mariano
| | > | >
| | > | > 2010/2/20 Miguel Enrique Cobá Martinez
| <[hidden email]>
| | > | >
| | > | > El vie, 19-02-2010 a las 14:14 -0800, Dale Henrichs escribió:
| | > | >> > Miguel,
| | > | >> >
| | > | >> > You have a good point ... I've already got something like
| | this
| | > | for the
| | > | >> GemStone release  process, where we create a directory-based
| | > | repository
| | > | >> containing all of the mcz needed to bootstrap a GLASS
| | > | configuration, so I
| | > | >> could adapt the algorithm to work for Metacello in general.
| | > | >> >
| | > | >> > I've submitted an issue about the progress bars ...
| | originally I
| | > | dumped
| | > | >> all of the progress info to the transcript, but folks who
| | don't
| | > | normally
| | > | >> open Transcripts complained about how long loads would take,
| so
| | put
| | > | in the
| | > | >> progress bars. Would it make sense to push the progress bars
| | into
| | > | the
| | > | >> Metacello tools group (i.e., OB-Metacello)?
| | > | >>
| | > | >> >  Loading OB-Metacello is an indication that you're in an
| | > | interactive
| | > | >> development image...Personally when I'm interactively
| loading
| | > | things I can
| | > | >> get a better feel for how far things have progressed with
| the
| | > | progress bars
| | > | >> than I can get from the Transcript...
| | > | >> >
| | > | >>
| | > | >>
| | > | >> Yes, I agree that there isn't anything better than a
| progress
| | bar
| | > | to get
| | > | >> the current state of a process. Just a simple usage like:
| | > | >>
| | > | >> my_build_script.st
| | > | >> Gofer new
| | > | >>        squeaksource: 'MetacelloRepository';
| | > | >>        package: 'ConfigurationOfPackage';
| | > | >>        load.
| | > | >>
| | > | >> ((Smalltalk at: #ConfigurationOfPackage) project version:
| | '1.0')
| | > | >>        silently: true; "or outputToTranscript: true"
| | > | >>        load.
| | > | >>
| | > | >> "Save as magma.image"
| | > | >> SmalltalkImage current saveAs: 'magma'.
| | > | >> SmalltalkImage current snapshot: true andQuit: true.
| | > | >>
| | > | >>
| | > | >> Where silently, if not specified is false, so that uses
| | progress
| | > | bar as
| | > | >> now. But when someone is scripting some image build, they
| | specify
| | > | it to
| | > | >> true so that the image just work "headless" in loading
| | packages.
| | > | >>
| | > | >> But Dale, I know that this particular change, even
| externally
| | is
| | > | simple,
| | > | >> is very intrusive changing calls to progress bar with calls
| to
| | log
| | > | to
| | > | >> transcript, so don't worry a lot for this. If someday is
| | > | implemented, it
| | > | >> will be good, if not, well, nothing is lost. The code works
| | > | correctly
| | > | >> and as good as it can be with the current behavior. Besides,
| | maybe
| | > | this
| | > | >> feature isn't really needed, I *think* that it will be
| useful
| | for
| | > | >> continuous integration and automatic builds of pharo images
| | where
| | > | the
| | > | >> complete log of the image building can be extracted to a
| file
| | and
| | > | shown
| | > | >> in the interface of the image building software (like
| mason).
| | But
| | > | it is
| | > | >> just what I think. Lukas or the people building the
| | infrastructure
| | > | will
| | > | >> have better opinions than mine.
| | > | >>
| | > | >> --
| | > | >> Miguel Cobá
| | > | >> http://miguel.leugim.com.mx
| | > | >>
| | > | >>
| | > | >
| | > |
| | > | To unsubscribe from this group, send email to
| | > | metacello+unsubscribegooglegroups.com or reply to this email
| with
| | the
| | > | words "REMOVE ME" as the subject.
| | >
| | > To unsubscribe from this group, send email to metacello+
| | > unsubscribegooglegroups.com or reply to this email with the words
| | "REMOVE
| | > ME" as the subject.
| | >
| |
| | To unsubscribe from this group, send email to
| | metacello+unsubscribegooglegroups.com or reply to this email with
| the
| | words "REMOVE ME" as the subject.
|
| To unsubscribe from this group, send email to metacello+
| unsubscribegooglegroups.com or reply to this email with the words
| "REMOVE
| ME" as the subject.
|
| To unsubscribe from this group, send email to
| metacello+unsubscribegooglegroups.com or reply to this email with the
| words "REMOVE ME" as the subject.

To unsubscribe from this group, send email to metacello+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.