[Glass] load ignoring gofer

Hi,

I'm trying to figure out why I'm getting "redirecting to
http://seaside.gemtalksystems.com/ss/(announcements|monticello|smtp|Seaside30)/?C=M;O=D"
when loading BaselineOfGLASS1 from a locally cloned repository.

We end up calling:

MetacelloProjectReferenceSpec | loadUsing: aLoader gofer: ignored

| required |
required := self resolveToLoadableSpec.
required loader: aLoader.
^required load

which, as the parameter name suggests, ignores the gofer. The sender
diligently sets the repositories, which are ignored in this method.

Should the implementation of this method perhaps change to use the
gofer? Or should it change to copy the repositories from the gofer and
set that on the "required". (This is a
MetacelloMCConfigurationOfProjectSpec, which understand repositories:
which can be extracted from the Gofer.)

Alternatively, it is the problem that we do end up with a
MetacelloProjectReferenceSpec, and we should be calling
#loadUsing:gofer: on something else.

So, I'll try something. See how it pans out.

Thanks
Otto
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Otto,

Don't change the implementation of MetacelloProjectReferenceSpec:)

I'm not sure why you are getting the redirected messages ... I don't  get any redirects when I install from github and I don't see any reason why a local repo would behave differently, so I'm curious why this is happening, could you supply with the log files perhaps there are some clues there ...

When you say that "you end up calling MetacelloProjectReferenceSpec | loadUsing: aLoader gofer: ignored" are you saying that you are directly calling that method from your own load code, or are you saying that you've traced this method to be the culprit?

So, logs and the load script would help me understand...

Dale


----- Original Message -----
| From: "Otto Behrens" <[hidden email]>
| To: [hidden email]
| Sent: Monday, November 18, 2013 6:59:15 AM
| Subject: [Glass] load ignoring gofer
|
| Hi,
|
| I'm trying to figure out why I'm getting "redirecting to
| http://seaside.gemtalksystems.com/ss/(announcements|monticello|smtp|Seaside30)/?C=M;O=D"
| when loading BaselineOfGLASS1 from a locally cloned repository.
|
| We end up calling:
|
| MetacelloProjectReferenceSpec | loadUsing: aLoader gofer: ignored
|
| | required |
| required := self resolveToLoadableSpec.
| required loader: aLoader.
| ^required load
|
| which, as the parameter name suggests, ignores the gofer. The sender
| diligently sets the repositories, which are ignored in this method.
|
| Should the implementation of this method perhaps change to use the
| gofer? Or should it change to copy the repositories from the gofer
| and
| set that on the "required". (This is a
| MetacelloMCConfigurationOfProjectSpec, which understand repositories:
| which can be extracted from the Gofer.)
|
| Alternatively, it is the problem that we do end up with a
| MetacelloProjectReferenceSpec, and we should be calling
| #loadUsing:gofer: on something else.
|
| So, I'll try something. See how it pans out.
|
| Thanks
| Otto
| _______________________________________________
| Glass mailing list
| [hidden email]
| http://lists.gemtalksystems.com/mailman/listinfo/glass
|
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

> Don't change the implementation of MetacelloProjectReferenceSpec:)

Ok, my attempts so for not working.

> I'm not sure why you are getting the redirected messages ... I don't  get any redirects when I install from github and I don't see any reason why a local repo would behave differently, so I'm curious why this is happening, could you supply with the log files perhaps there are some clues there ...

Attached...

Remember I start with the shipped seaside extent.

the runtime stuff is just loading the ConfigurationOf ...

> When you say that "you end up calling MetacelloProjectReferenceSpec | loadUsing: aLoader gofer: ignored" are you saying that you are directly calling that method from your own load code, or are you saying that you've traced this method to be the culprit?

I traced it and ended up there

Thanks

_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

PS. I also did this to get it through:
https://github.com/dalehenrich/metacello-work/pull/217
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Cool! Looks consistent with the direction I've been heading with that puppy .. we'll wait and see what travis thinks[1]:)

I really appreciate the contribution!

Dale

[1] https://travis-ci.org/dalehenrich/metacello-work/builds/14151564

----- Original Message -----
| From: "Otto Behrens" <[hidden email]>
| To: "Dale K. Henrichs" <[hidden email]>
| Cc: [hidden email]
| Sent: Monday, November 18, 2013 9:44:32 AM
| Subject: Re: [Glass] load ignoring gofer
|
| PS. I also did this to get it through:
| https://github.com/dalehenrich/metacello-work/pull/217
|
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass

Otto,

Okay...the redirects are coming during the load of Grease which is done as a pre-requisite to GLASS1 ... I typically do an upgrade to 1.0-beta.9.1 before loading GLASS1 so the redirectiion happens during that step as Grease is updated in that process ...

So if you make the newer version of Grease available from your third party repos, then the GLASS1 load should be self contained. If you look at the GLASS1 baseline GoferProjectLoader, Grease and XMLSupport still reference external http-based repositories.

I've got a first cut sample project with a couple of dependent projects, but I just realized that for completeness I should add a Confgiguration-based project that gets locked so I'll have to gen up another dummy project for that ...

Dale
----- Original Message -----
| From: "Otto Behrens" <[hidden email]>
| To: "Dale K. Henrichs" <[hidden email]>
| Cc: [hidden email]
| Sent: Monday, November 18, 2013 8:57:15 AM
| Subject: Re: [Glass] load ignoring gofer
|
| > Don't change the implementation of MetacelloProjectReferenceSpec:)
|
| Ok, my attempts so for not working.
|
| > I'm not sure why you are getting the redirected messages ... I
| > don't  get any redirects when I install from github and I don't
| > see any reason why a local repo would behave differently, so I'm
| > curious why this is happening, could you supply with the log files
| > perhaps there are some clues there ...
|
| Attached...
|
| Remember I start with the shipped seaside extent.
|
| the runtime stuff is just loading the ConfigurationOf ...
|
| > When you say that "you end up calling MetacelloProjectReferenceSpec
| > | loadUsing: aLoader gofer: ignored" are you saying that you are
| > directly calling that method from your own load code, or are you
| > saying that you've traced this method to be the culprit?
|
| I traced it and ended up there
|
| Thanks
|
_______________________________________________
Glass mailing list
[hidden email]
http://lists.gemtalksystems.com/mailman/listinfo/glass