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" <stephane.ducasse@inria.fr> 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" <renggli@gmail.com> 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 | > | Pharo-project@lists.gforge.inria.fr | > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

On Mon, Dec 28, 2009 at 4:39 PM, Stéphane Ducasse <stephane.ducasse@inria.fr

wrote:

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.

the proposal is in Java or SQL ? hahahah NILLLLLLLLLLLLL :)

Stef

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

...

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" <stephane.ducasse@inria.fr> 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" <renggli@gmail.com> 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 | > | Pharo-project@lists.gforge.inria.fr | > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project@lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project