Hi Hilaire,
I also use a command line handler for start in a new image with voyage . I
start it like this on windows:
.\...\Pharo5.0.image --no-default-preferences eval --save "
MCRepositoryGroup default addRepository: (MCHttpRepository location: '
http://smalltalkhub.com/mc/Sabine/RKA24/main'
Hi Sabine,
Thanks to share your experience.
My process is in 3 folds:
1. I build from bash and smalltalk scripts an application archive for
deployment, as I do for Dr.Geo (with configured image, VM, bootstart
data and bash scripts)
2. On the target host, the archive is deployed (unarchived),
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
I try with the modified configure:
spec project: 'voyage' with: [
spec
className: 'ConfigurationOfVoyageMongo';
repository:
'http://www.smalltalkhub.com/mc/estebanlm/Voyage/main';
This is really strange. Because according to the survey every 2 our of 3
participants identified Smalltalk as a language they love. However I’d say that
only 1 of every 20 developers that I meet knows what Smalltalk is.
Uko
> On 24 Mar 2017, at 13:38, Cyril Ferlicot D.
In Pharo 6 I select some code and then from menu choose Suggestions
ExtractMethod
If the code is one line it sometimes works but after the first fail it
then logs "Could not extract code from method'
If it has multiple lines including onbe message over lines I get a
debugger call back
In
Hi Everyone,
Would someone please point me to instructions on how to build the 6.0
threaded VM for linux (Ubuntu).
Thanks!
Alistair
Nice ! But do you have a way to automatize this process ? ;-)
Envoyé de mon iPhone
> Le 25 mars 2017 à 18:21, Stephan Eggermont a écrit :
>
>> On 25/03/17 16:26, Ben Coman wrote:
>>
>> Now what might be an good marketing hack would be a live video showing...
>> * downloading
Hi mark
this is probably a bug.
Also the smart suggestions would need another pass to better integrate
them.
Can you open a bug entry? Now we are busy so this is not clear that it will
be fixed.
Stef
On Sat, Mar 25, 2017 at 6:08 PM, Mark Bestley wrote:
> In Pharo 6 I
Hilaire
you should think to move to Pharo 50. We closed around 1500 issues between
pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60.
Pharo 50 is really stable and working well
Stef
On Sat, Mar 25, 2017 at 8:58 AM, Hilaire wrote:
> Hi Sabine,
>
> Thanks
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:
On 25/03/17 16:26, Ben Coman wrote:
Now what might be an good marketing hack would be a live video showing...
* downloading StackOverflow survey data via Zinc,
* browsing returned data with GTInspector,
* in the debugger, creating/molding some basic classes around the data,
* graphing the data
Hi,
something like this:
$ git clone https://github.com/pharo-project/pharo-vm.git
$ cd pharo-vm/opensmalltalk-vm/build.linux32x86/pharo.cog.spur/build
$ ./mvm
you will be ok as long as you provide the requirements (taken from travis):
addons:
apt:
packages:
- debhelper
-
On Sun, Mar 26, 2017 at 1:13 AM, Alistair Grant wrote:
> Hi Everyone,
>
> Would someone please point me to instructions on how to build the 6.0
> threaded VM for linux (Ubuntu).
Looking here...
Hi Esteban & Ben,
Thanks very much for your quick replies.
Both versions are failing trying to build libssl.so, see error messages
below.
The build output is huge, so I've only included the final few lines (a
but more in Ben's build).
My familiarity with makefiles is bad enough, and have never
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:
guille and santiago have a worker pool that is planned to serialize test
running locally before commit
based on taskIt.
On Sat, Mar 25, 2017 at 7:56 PM, Stephan Eggermont wrote:
> On 25/03/17 18:29, serge.stinckw...@gmail.com wrote:
>
>> Nice ! But do you have a way to
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
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
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
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
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.
On 25/03/17 18:29,
serge.stinckw...@gmail.com wrote:
Nice ! But do you have a way to automatize this process ? ;-)
How difficult can it be? We did it 18 years ago in java & delphi :)
Stephan
> 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
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
On Sat, Mar 25, 2017 at 07:29:29PM +0100, Alistair Grant wrote:
> make[3]: *** No rule to make target
> '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'.
Try:
% sudo apt-get install libssl1.0.0:i386
Pierce
On Sat, Mar 25, 2017 at 07:29:29PM +0100, Alistair Grant wrote:
> make[3]: *** No rule to make target
> '/usr/lib/i386-linux-gnu/libssl.so', needed by 'libgit2.so.0.23.0'.
Sorry, also
% sudo apt-get install libssl-dev:i386
On Sat, Mar 25, 2017 at 07:56:03PM +0100, Stephan Eggermont wrote:
> On 25/03/17 18:29, serge.stinckw...@gmail.com wrote:
> >Nice ! But do you have a way to automatize this process ? ;-)
> How difficult can it be? We did it 18 years ago in java & delphi :)
I was going to answer 'Hadoop!', then
28 matches
Mail list logo