Hi Hilaire,
thing is:
1) you use github project, then the baseline
spec
baseline: ‘Voyage’
with: [ spec repository: 'github://pharo-nosql/voyage/mc
<github://pharo-nosql/voyage/mc>’ ].
2) or you use the metarepo configuration
spec project: 'voyage' with: [
spec
className: 'ConfigurationOfVoyageMongo';
repository:
'http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main’ ].
why this one is not fully functional?
then aside that… one thing I do not understand is why you are develop a new
project with an old (and not maintained anymore) Pharo version?
Currently supported version is Pharo5, and even if Voyage is an external
project, usually development follows Pharo stable version…
cheers!
Esteban
> On 25 Mar 2017, at 11:16, Hilaire <hila...@drgeo.eu> wrote:
>
> I try with the modified configure:
>
> spec project: 'voyage' with: [
> spec
> className: 'ConfigurationOfVoyageMongo';
> repository:
> 'http://www.smalltalkhub.com/mc/estebanlm/Voyage/main';
> versionString: #stable.
> ].
>
>
> But it does not work either. Error at installation this time. Can'find
> ALL...
>
>
> Then I tried this one:
>
> spec project: 'voyage' with: [
> spec
> className: 'ConfigurationOfVoyageMongo';
> repository:
> 'http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPharo60/main';
> versionString: #stable.
> ].
>
>
> In all case the installed Voyage is not fully fonctionnal
>
>
> It is weird because my dev image is 4.0 Pharo based, and Voyage was
> installed from the MetaRepoForPharo60
>
>
> Any ideas
>
> Hilaire
>
>
> Le 25/03/2017 à 10:47, Hilaire a écrit :
>> My configure baseline is just as simple as the one bellow.
>> All is loaded fine but Voyage.
>
> --
> Dr. Geo
> http://drgeo.eu
>
>
