Issue with gofer/metacello

Lukas,

With Gofer-dkh.105, I was able to survive the upgrade from Gofer-lr.83 to Gofer-dkh.105. Gofer-lr.83 was the base version of Gofer used during bootstrapping. The change that broke the camel's back was removing the #version iv from GoferOperation. preGofer-dkh.105 there was no accessor for #version so direct access was required. postGofer-dkh.105 an accessor is required and the loader is used as part of the loading process and my subclass of the loader is there to smooth over the changes that have been made to the Gofer API over time - the code in Metacello needs to be able to run both before and after a new version of Gofer is installed.

If we had true "atomic load" we'd be able to survive this set of changes, but without it I'm not sure what can be done other than using different bootstrapping code depending upon which version of Gofer is loaded ... which bangs into the other changes to the API that have been made since Gofer-lr.83.

Gofer-lr.83 dates back to pharo1.0-10493 which is when Gofer started to be pre-loaded into the RC1 images.

There appear to be versionNumber parsing errors in the older versions of Gofer, that prevent me from using Gofer to determine which package is loaded, so I may have to resort to direct Monticello access to detect the loaded package versions, either that or some kind of check as the the methods that are available in Gofer and infer the "version" of Gofer that is loaded ...

Once I have my hands on the "version" of Gofer that is loaded, I can arrange to have the correctly compatible Metacello code loaded on top and we're off to the races.

Dale


----- "Stéphane Ducasse" <[hidden email]> wrote:

| argh!
| lukas is it possible to lower the pain of dale?
|
| Stef
|
| On Dec 27, 2009, at 10:27 PM, Dale Henrichs wrote:
|
| > The latest Gofer API is not backward compatible with the earlier
| versions of the Gofer API. This means that I need to have different
| versions of Metacello to use with the different versions of Gofer.
| Unfortunately, I can't use Gofer to detect which version of Gofer is
| loaded because of the API changes. So I will have to write more code
| than I'd like to detect which version of Gofer is pre-installed. The
| API changes also impact the bootstrapping code.
| >
| > Solving these problems are a larger project than I can undertake on
| a Sunday and I _am_ on vacation the coming week as well.
| >
| > So until further notice, if you want to use Metacello 1.0-beta.17
| (or earlier) in Pharo you will have to manually ensure Gofer-lr.83 (or
| earlier) is loaded into your image before attempting to load any
| Metacello configurations. I'm not sure that you use Gofer to load an
| earlier version of itself (I'll be finding out in the next few
| days)...
| >
| > Metacello 1.0-beta.18 works with Gofer-lr.107 (in pharo 1.0-10502).
| If you want to use Metacello 1.0-beta.18 (currently in development, so
| it's subject to change). You will have to manually bootstrap Metacello
| by executing:
| >
| >  Gofer new
| >    gemsource: 'metacello';
| >    package: 'ConfigurationOfMetacello';
| >    load.
| >  (Smalltalk at: #ConfigurationOfMetacello) perform:
| #ensureMetacello18.
| >  ((Smalltalk at: #ConfigurationOfMetacello) project version:
| '1.0-beta.18') load: 'ALL'.
| >
| > before loading your configuration.
| >
| > I won't release 1.0-beta.18 until I've resolved the bootstrapping
| problem. I'm pretty sure that there is a technical solution, but it
| will take several days for me to get it implemented.
| >
| > Dale
| >
| > ----- "Dale Henrichs" <[hidden email]> wrote:
| >
| > | Version 1.0-beta.18 (development) should have fixes for the
| latest
| > | Gofer. 1.0-beta.18 is currently in #development so it is
| automatically
| > | loaded. When I get the chance to test the Metacello fixes with
| 10502,
| > | I'll #release 1.0-beta.18 (and will be automatically loaded).
| > |
| > | Dale
| > | ----- "Alexandre Bergel" <[hidden email]> wrote:
| > |
| > | | Hi Lukas,
| > | |
| > | | In a fresh 10502 I evaluated:
| > | | -=-=-=-=-=-=-=-=-=
| > | |   [ Gofer gofer load ]
| > | |        on: Error
| > | |        do: [ :err | err retry ].
| > | |    Gofer gofer recompile.
| > | | Gofer new
| > | | squeaksource: 'Mondrian';
| > | | addPackage: 'ConfigurationOfMondrian';
| > | | load.
| > | | (Smalltalk at: #ConfigurationOfMondrian) perform:
| #loadLastStable.
| > | | -=-=-=-=-=-=-=-=-=
| > | |
| > | | I have the same error.
| > | | The error comes from:
| > | |
| > | | -=-=-=-=-=-=-=-=-=
| > | | MetacelloMCProject>>updateProject
| > | | "load the latest version of the configuration package"
| > | |
| > | | | mcLoader |
| > | | (mcLoader := self loader) == nil
| > | | ifTrue: [ mcLoader := self project loaderClass on: nil ].
| > | | mcLoader doingLoads: [
| > | | | gofer |
| > | | gofer := Gofer new.
| > | | MCWorkingCopy
| > | | managersForClass: self configuration class
| > | | do: [:mgr |
| > | | gofer add: (GoferPackageReference name: mgr packageName  
| > | | repository: mgr repositoryGroup) versionReference.
| > | | Transcript cr; show: 'Loading -> ', mgr packageName, ' <-'
| ].
| > | | gofer load ].
| > | | ^true
| > | | -=-=-=-=-=-=-=-=-=
| > | |
| > | | Cheers,
| > | | Alexandre
| > | |
| > | | On 27 Dec 2009, at 17:27, Lukas Renggli wrote:
| > | |
| > | | >> After proceeding these warnings, I have a rollback: MNU
| > | | >> GoferPackageReference class>>name:repository:
| > | | >
| > | | > Can you evaluate
| > | | >
| > | | >   [ Gofer gofer load ]
| > | | >       on: Error
| > | | >       do: [ :err | err retry ].
| > | | >   Gofer gofer recompile.
| > | | >
| > | | > ? I don't have any senders of #name:repository: to  
| > | | > GoferPackageReference.
| > | | >
| > | | > Lukas
| > | | >
| > | | > --
| > | | > Lukas Renggli
| > | | > http://www.lukas-renggli.ch
| > | | >
| > | | > _______________________________________________
| > | | > Pharo-project mailing list
| > | | > [hidden email]
| > | | >
| > |
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| > | | >
| > | |
| > | | --
| > | | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
| > | | Alexandre Bergel  http://www.bergel.eu
| > | | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
| > | |
| > | |
| > | |
| > | |
| > | |
| > | |
| > | | _______________________________________________
| > | | Pharo-project mailing list
| > | | [hidden email]
| > | |
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| > |
| > | _______________________________________________
| > | Pharo-project mailing list
| > | [hidden email]
| > |
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| >
| > _______________________________________________
| > Pharo-project mailing list
| > [hidden email]
| > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Gofer-dkh.105 or whichever later version predates the move of the instance variable would get Metacello back into a bootable form for all versions of Pharo.

I agree that for 1.0 a stable version of Gofer be chosen ... I'm trying to restrict the current Metacello changes to avoid significant API changes, but every time Gofer moves out from under me, I'm forced into making fundamental changes.


Dale
----- "Lukas Renggli" <[hidden email]> wrote:

| >> | | >> After proceeding these warnings, I have a rollback: MNU
| >> | | >> GoferPackageReference class>>name:repository:
| >> | | >
| >> | | > Can you evaluate
| >> | | >
| >> | | >   [ Gofer gofer load ]
| >> | | >       on: Error
| >> | | >       do: [ :err | err retry ].
| >> | | >   Gofer gofer recompile.
| >> | | >
| >> | | > ? I don't have any senders of #name:repository: to
| >> | | > GoferPackageReference.
|
| We can remove the deprecated warnings, but that will not solve the
| real problem. Metacello is using some internal parts of Gofer that
| had
| to be changed to properly support fetch/push operations on multiple
| repositories.
|
| People have to stick with an old version of Gofer/Monticello. That's
| the same as with Pharo 1.1: Do not use the latest one.
|
| Lukas
|
| --
| Lukas Renggli
| http://www.lukas-renggli.ch
|
| _______________________________________________
| Pharo-project mailing list
| [hidden email]
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Dec 27, 2009, at 11:38 PM, Dale Henrichs wrote:

> Gofer-dkh.105 or whichever later version predates the move of the instance variable would get Metacello back into a bootable form for all versions of Pharo.
>
> I agree that for 1.0 a stable version of Gofer be chosen ... I'm trying to restrict the current Metacello changes to avoid significant API changes, but every time Gofer moves out from under me, I'm forced into making fundamental changes.

Yes!
I would like to have gofer stable in 1.0 and the same in 1.1
Sorry for the moving sands ;(
Stef


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Stef,

The moving sands are one of the costs of advancement ... I'm more upset that _I_ don't have time to solve the dang problems than I am that the problems are appearing ... all of the changes have been for good reasons and over time I have been removing code from Metacello as Gofer has expanded it's functionality...

Gotta love the holidays:)

Dale
----- "Stéphane Ducasse" <[hidden email]> wrote:

| On Dec 27, 2009, at 11:38 PM, Dale Henrichs wrote:
|
| > Gofer-dkh.105 or whichever later version predates the move of the
| instance variable would get Metacello back into a bootable form for
| all versions of Pharo.
| >
| > I agree that for 1.0 a stable version of Gofer be chosen ... I'm
| trying to restrict the current Metacello changes to avoid significant
| API changes, but every time Gofer moves out from under me, I'm forced
| into making fundamental changes.
|
| Yes!
| I would like to have gofer stable in 1.0 and the same in 1.1
| Sorry for the moving sands ;(
| Stef
|
| > Dale
| > ----- "Lukas Renggli" <[hidden email]> wrote:
| >
| > | >> | | >> After proceeding these warnings, I have a rollback: MNU
| > | >> | | >> GoferPackageReference class>>name:repository:
| > | >> | | >
| > | >> | | > Can you evaluate
| > | >> | | >
| > | >> | | >   [ Gofer gofer load ]
| > | >> | | >       on: Error
| > | >> | | >       do: [ :err | err retry ].
| > | >> | | >   Gofer gofer recompile.
| > | >> | | >
| > | >> | | > ? I don't have any senders of #name:repository: to
| > | >> | | > GoferPackageReference.
| > |
| > | We can remove the deprecated warnings, but that will not solve
| the
| > | real problem. Metacello is using some internal parts of Gofer
| that
| > | had
| > | to be changed to properly support fetch/push operations on
| multiple
| > | repositories.
| > |
| > | People have to stick with an old version of Gofer/Monticello.
| That's
| > | the same as with Pharo 1.1: Do not use the latest one.
| > |
| > | Lukas
| > |
| > | --
| > | Lukas Renggli
| > | http://www.lukas-renggli.ch
| > |
| > | _______________________________________________
| > | Pharo-project mailing list
| > | [hidden email]
| > |
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| >
| > _______________________________________________
| > Pharo-project mailing list
| > [hidden email]
| > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Yes

I'm losing my time trying to rescue a proposal we should sent and I wonder what I'm doing because the acceptance rate are null.

Stef

On Dec 28, 2009, at 4:20 PM, Dale Henrichs wrote:


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

I haven't found a better way to load Mondrian in the last Pharo than  
this incantation:
-=-=-=-=-=-=-=-=-=-=-=-=
[Gofer new renggli: 'gofer'; version: 'Gofer-lr.86'; load] on: Error  
do: [].
Gofer new
        squeaksource: 'Mondrian';
        addPackage: 'ConfigurationOfMondrian';
        load.
(Smalltalk at: #ConfigurationOfMondrian) perform: #loadDefault.
-=-=-=-=-=-=-=-=-=-=-=-=

Cheers,
Alexandre

On 27 Dec 2009, at 18:35, Tudor Girba wrote:

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

I've been able to address the problems with Metacello and pharo1.0-10502-rc1dev09.12.2. Version 1.0-beta.18 (just released see: http://groups.google.com/group/metacello/msg/a12918b4bd11c0ef for the announcement) has been tested with both:
  - pharo1.0-10493-rc1dev09.11.2
  - pharo1.0-10502-rc1dev09.12.2

the class-side #ensureMetacello methods for configurations also need to be updated to work with pharo1.0-10502-rc1dev09.12.2. See: http://code.google.com/p/metacello/wiki/EnsureMetacello for a suggested implementation.

I plan to update the #ensureMetacello methods for the configurations in MetacelloRepository tonight.

Dale
----- "Dale Henrichs" <[hidden email]> wrote:

| The latest Gofer API is not backward compatible with the earlier
| versions of the Gofer API. This means that I need to have different
| versions of Metacello to use with the different versions of Gofer.
| Unfortunately, I can't use Gofer to detect which version of Gofer is
| loaded because of the API changes. So I will have to write more code
| than I'd like to detect which version of Gofer is pre-installed. The
| API changes also impact the bootstrapping code.
|
| Solving these problems are a larger project than I can undertake on a
| Sunday and I _am_ on vacation the coming week as well.
|
| So until further notice, if you want to use Metacello 1.0-beta.17 (or
| earlier) in Pharo you will have to manually ensure Gofer-lr.83 (or
| earlier) is loaded into your image before attempting to load any
| Metacello configurations. I'm not sure that you use Gofer to load an
| earlier version of itself (I'll be finding out in the next few
| days)...
|
| Metacello 1.0-beta.18 works with Gofer-lr.107 (in pharo 1.0-10502). If
| you want to use Metacello 1.0-beta.18 (currently in development, so
| it's subject to change). You will have to manually bootstrap Metacello
| by executing:
|
|   Gofer new
|     gemsource: 'metacello';
|     package: 'ConfigurationOfMetacello';
|     load.
|   (Smalltalk at: #ConfigurationOfMetacello) perform:
| #ensureMetacello18.
|   ((Smalltalk at: #ConfigurationOfMetacello) project version:
| '1.0-beta.18') load: 'ALL'.
|
| before loading your configuration.
|
| I won't release 1.0-beta.18 until I've resolved the bootstrapping
| problem. I'm pretty sure that there is a technical solution, but it
| will take several days for me to get it implemented.
|
| Dale
|
| ----- "Dale Henrichs" <[hidden email]> wrote:
|
| | Version 1.0-beta.18 (development) should have fixes for the latest
| | Gofer. 1.0-beta.18 is currently in #development so it is
| automatically
| | loaded. When I get the chance to test the Metacello fixes with
| 10502,
| | I'll #release 1.0-beta.18 (and will be automatically loaded).
| |
| | Dale
| | ----- "Alexandre Bergel" <[hidden email]> wrote:
| |
| | | Hi Lukas,
| | |
| | | In a fresh 10502 I evaluated:
| | | -=-=-=-=-=-=-=-=-=
| | |   [ Gofer gofer load ]
| | |        on: Error
| | |        do: [ :err | err retry ].
| | |    Gofer gofer recompile.
| | | Gofer new
| | | squeaksource: 'Mondrian';
| | | addPackage: 'ConfigurationOfMondrian';
| | | load.
| | | (Smalltalk at: #ConfigurationOfMondrian) perform:
| #loadLastStable.
| | | -=-=-=-=-=-=-=-=-=
| | |
| | | I have the same error.
| | | The error comes from:
| | |
| | | -=-=-=-=-=-=-=-=-=
| | | MetacelloMCProject>>updateProject
| | | "load the latest version of the configuration package"
| | |
| | | | mcLoader |
| | | (mcLoader := self loader) == nil
| | | ifTrue: [ mcLoader := self project loaderClass on: nil ].
| | | mcLoader doingLoads: [
| | | | gofer |
| | | gofer := Gofer new.
| | | MCWorkingCopy
| | | managersForClass: self configuration class
| | | do: [:mgr |
| | | gofer add: (GoferPackageReference name: mgr packageName  
| | | repository: mgr repositoryGroup) versionReference.
| | | Transcript cr; show: 'Loading -> ', mgr packageName, ' <-' ].
| | | gofer load ].
| | | ^true
| | | -=-=-=-=-=-=-=-=-=
| | |
| | | Cheers,
| | | Alexandre
| | |
| | | On 27 Dec 2009, at 17:27, Lukas Renggli wrote:
| | |
| | | >> After proceeding these warnings, I have a rollback: MNU
| | | >> GoferPackageReference class>>name:repository:
| | | >
| | | > Can you evaluate
| | | >
| | | >   [ Gofer gofer load ]
| | | >       on: Error
| | | >       do: [ :err | err retry ].
| | | >   Gofer gofer recompile.
| | | >
| | | > ? I don't have any senders of #name:repository: to  
| | | > GoferPackageReference.
| | | >
| | | > Lukas
| | | >
| | | > --
| | | > Lukas Renggli
| | | > http://www.lukas-renggli.ch
| | | >
| | | > _______________________________________________
| | | > Pharo-project mailing list
| | | > [hidden email]
| | | >
| | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| | | >
| | |
| | | --
| | | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
| | | Alexandre Bergel  http://www.bergel.eu
| | | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
| | |
| | |
| | |
| | |
| | |
| | |
| | | _______________________________________________
| | | Pharo-project mailing list
| | | [hidden email]
| | |
| http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
| |
| | _______________________________________________
| | Pharo-project mailing list
| | [hidden email]
| | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project