Smalltalk › Pharo › Pharo Smalltalk Developers

Comments on Metacello and ConfigurationOfExternalWebBrowser

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

Torsten Bergmann

Comments on Metacello and ConfigurationOfExternalWebBrowser

>Two little remarks of the conf: you are using for FFI '1.0-baseline', not a
>version, this means that it will ALWAYS bring the latest version (maybe
>unstable). That's why I always try to put a particular version that I know
>is stable.

Thought about that again and looked at other examples.

Now the baseline of ExternalWebbrowser depends on a baseline
of FFI. And the version itself uses the version.
See ConfiguratonOfExternalWebBrowser-tbn-5.mcz

This is similar to what Dale did in the seaside 3.0 config with
grease and follows the rules from #lesson11Blessing:

"Since the latest #baseline version should reflect the most
up-to-date project structure, ... should load the absolute
bleeding edge of the project."

>Come on!!! That's not an excuse ;)

Have access now - typos in the tutorial are fixed. Included
in 1.0-beta.20 of metacello conf.

Just run
"ConfigurationOfMetacello loadLatestPackages"

Bye
T.
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

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

Mariano Martinez Peck

Re: Comments on Metacello and ConfigurationOfExternalWebBrowser

On Thu, Jan 14, 2010 at 9:53 AM, Torsten Bergmann <[hidden email]> wrote:

>Two little remarks of the conf: you are using for FFI '1.0-baseline', not a
>version, this means that it will ALWAYS bring the latest version (maybe
>unstable). That's why I always try to put a particular version that I know
>is stable.

Thought about that again and looked at other examples.

Now the baseline of ExternalWebbrowser depends on a baseline
of FFI. And the version itself uses the version.
See ConfiguratonOfExternalWebBrowser-tbn-5.mcz

Torsten: Maybe it is not correct what I do but in your case, for example, I wouldn't put the baseline of FFI.

    project: 'FFI' with: [
                spec
                    className: 'ConfigurationOfFFI';
                    file: 'ConfigurationOfFFI';
                    version: '1.0-baseline';
                    repository: 'http://www.squeaksource.com/MetacelloRepository' ].

I don't like to put ANYTHING related to version or baselines in a baseline method. I just want to put dependencies, groups, etc. So I would write:

    project: 'FFI' with: [
                spec
                    className: 'ConfigurationOfFFI';
                    file: 'ConfigurationOfFFI';
                    repository: 'http://www.squeaksource.com/MetacelloRepository' ].

Then, in the version method, I would put exactly what you did:

spec
            project: 'FFI' with: '1.0'.


So...in summary, form my point of view, is not necessary to put the baseline when defining the dependency to FFI.

I insist that you should also send this kind of mails to Metacello mailing list :)

This is similar to what Dale did in the seaside 3.0 config with
grease and follows the rules from #lesson11Blessing:

"Since the latest #baseline version should reflect the most
up-to-date project structure, ... should load the absolute
bleeding edge of the project."

>Come on!!! That's not an excuse ;)

Have access now - typos in the tutorial are fixed. Included
in 1.0-beta.20 of metacello conf.

Just run
"ConfigurationOfMetacello loadLatestPackages"

Coooool!!! Excellent. Thank you very much :)

Bye
T.
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

_______________________________________________
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