Thanks for the tip but I know that. I have full access to the voyage code.
Without knowing the reason and context an issue is useless.
Norbert
> Am 26.03.2017 um 19:35 schrieb Stephane Ducasse :
>
> Add an issue in the Voyage github repo and do a pull request to push esteban
> releasing a new
Add an issue in the Voyage github repo and do a pull request to push
esteban
releasing a new version.
On Sun, Mar 26, 2017 at 1:15 PM, Norbert Hartl wrote:
> I get that same problem, too, every time I do "Software update". But never
> understood the rationale of dropping a database at this poin
I get that same problem, too, every time I do "Software update". But never
understood the rationale of dropping a database at this point. I think we
should remove this line
Norbert
> Am 25.03.2017 um 22:04 schrieb Hilaire :
>
> ah yeah, I wrote an internal durty hack to get it rolling
>
> cle
ah yeah, I wrote an internal durty hack to get it rolling
cleanUp: aRepository
(aRepository isKindOf: Boolean) ifFalse: [ aRepository dropDatabase]
Le 25/03/2017 à 21:46, Hilaire a écrit :
> It occurs in Pharo5, likely not in Pharo4, or may be I fixed in my
> image, I don't remember.
--
Dr. Ge
More precisely with:
SmalltalkImage current cleanUp: true except: #() confirming: false.
It occurs in Pharo5, likely not in Pharo4, or may be I fixed in my
image, I don't remember.
Hilaire
Le 25/03/2017 à 21:33, Hilaire a écrit :
> I think there is a bug in Voyage when an image clean up is requ
I think there is a bug in Voyage when an image clean up is requested.
There is a confusion with the #cleanUp: message.
Hilaire
Le 25/03/2017 à 21:26, Hilaire a écrit :
> As A matter of fact, I ran the installation script with a Pharo5 image,
> and now I get another error during the installation p
Indeed, as I wrote in a previous email, this is how I got Voyage
installed too in my Pharo4 devel environment, and it went fine too.
Therefore the configuration should be ok. So this is weird.
It should not be package cache related because I build image with a
completely emptied build directory en
I just did this:
Gofer new
smalltalkhubUser: 'Pharo' project: 'MetaRepoForPharo60';
configurationOf: 'VoyageMongo';
loadStable.
(which is the same to the one you did)
in a fresh Pharo4 and it loaded fine. No UnQLite (which is correct).
Now, I guess Metacello looks for al
Hilaire
Yes you can load and old version and it should behave with the old behavior
and
potentially old bugs. You have the right. This is what a configuration
gives you.
Now esteban has the right to only add features and fix bugs in the
maintained versions.
And he could also consider that he does
> On 25 Mar 2017, at 19:46, Hilaire wrote:
>
> It is not a new project. It started with Pharo3. Then I see no reason
> why I can't load the Voyage code of the time of Pharo4, with the
> matching code version. It should be still there, is not the purpose of
> Configuration? Or may be I misunderst
Ok I try this configuration, looks like he wants to install UnQLite. See
debug log.
Hilaire
Le 25/03/2017 à 18:08, Esteban Lorenzano a écrit :
>
> spec project: 'voyage' with: [
> spec
> className: 'ConfigurationOfVoyageMongo';
> repository: 'http://www.smalltalkhub.com/mc/Pharo/MetaRepoForPhar
It is not a new project. It started with Pharo3. Then I see no reason
why I can't load the Voyage code of the time of Pharo4, with the
matching code version. It should be still there, is not the purpose of
Configuration? Or may be I misunderstand how version is working and its
purpose.
Hilaire
L
Hi Hilaire,
thing is:
1) you use github project, then the baseline
spec
baseline: ‘Voyage’
with: [ spec repository: 'github://pharo-nosql/voyage/mc
’ ].
2) or you use the metarepo configuration
spec project: 'voyage' with: [
spec
className: 'Configu
I try with the modified configure:
spec project: 'voyage' with: [
spec
className: 'ConfigurationOfVoyageMongo';
repository:
'http://www.smalltalkhub.com/mc/estebanlm/Voyage/main';
When I follow the procedure at https://github.com/pharo-nosql/voyage
to install Voyage in a 4.0 image, it leads to an unfonctonnal Voyage
(timeout on socket when doing a query)
My configure baseline is just as simple as the one bellow.
All is loaded fine but Voyage.
Any suggestion?
Hilaire
b
15 matches
Mail list logo
