On Sat, Apr 15, 2017 at 8:53 PM, Luke Gorrie wrote:
> On 15 April 2017 at 14:45, Esteban Lorenzano wrote:
>>
>> this belongs to pharo-dev, please continue there :)
>
>
> Looks to me like I should make a small replacement for mvm that is for nix.
>
> Nix indeed does its own thing.
>
> The downside
Whoops, now copied to pharo-dev to continue discussion there.
On Sun, Apr 16, 2017 at 9:13 PM, Ben Coman wrote:
> On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie wrote:
>>
>> On 14 April 2017 at 22:20, Stephane Ducasse wrote:
>>>
>>> This is what we always have when we release and we freeze it.
>
On Sat, Apr 15, 2017 at 12:43 PM, Luke Gorrie wrote:
>
> On 14 April 2017 at 22:20, Stephane Ducasse wrote:
>>
>> This is what we always have when we release and we freeze it.
>> The vm 60 will be compatible with latest pharo 60 image.
>
>
> It is possible that I have misunderstood the whole situ
On 15 April 2017 at 14:45, Esteban Lorenzano wrote:
> this belongs to pharo-dev, please continue there :)
>
Looks to me like I should make a small replacement for mvm that is for nix.
Nix indeed does its own thing.
The downside is that it's restricted: the build runs in a sandbox, can't
touch
this belongs to pharo-dev, please continue there :)
> On 15 Apr 2017, at 14:25, Alistair Grant wrote:
>
> On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke Gorrie wrote:
>> On 15 April 2017 at 11:53, Alistair Grant wrote:
>>
>>(actually, I'm not sure why you're bothering since 6 should
>>
On Sat, Apr 15, 2017 at 02:14:26PM +0200, Luke Gorrie wrote:
> On 15 April 2017 at 11:53, Alistair Grant wrote:
>
> (actually, I'm not sure why you're bothering since 6 should
> be out before the end of the month, but that's your choice :-)).
>
>
> I just want something stable and reaso
On 15 April 2017 at 11:53, Alistair Grant wrote:
> (actually, I'm not sure why you're bothering since 6 should
> be out before the end of the month, but that's your choice :-)).
>
I just want something stable and reasonably modern for running existing
applications and building new ones.
If that
On Sat, Apr 15, 2017 at 09:53:49AM +, Alistair Grant wrote:
>
> If you just want to build a single V6 pharo executable (no scripts,
> linux 64 bit in the example below):
>
> --
> #!/bin/bash
> set -e
>
> git clone https://github.com/pharo-project/pharo-vm.git
> git checkout
> cd pharo-vm/op
On Friday 14 April 2017 03:39 PM, Luke Gorrie wrote:
- The latest Pharo VM source release is compatible with the latest Pharo
image.
This is too strong a condition. For the OS, an image is just a
filesystem within a file. It is sufficient if the VM does not use the
same executable name if it
Hi Luke,
On Sat, Apr 15, 2017 at 10:34:31AM +0200, Luke Gorrie wrote:
> On 15 April 2017 at 10:08, Alistair Grant wrote:
>
> How about trying:
>
> $ git clone https://github.com/pharo-project/pharo-vm.git
> $ cd pharo-vm
> $ git checkout b8ec25a570d7539653e1d793e97609adb509aaed
On 15 April 2017 at 10:08, Alistair Grant wrote:
> How about trying:
>
> $ git clone https://github.com/pharo-project/pharo-vm.git
> $ cd pharo-vm
> $ git checkout b8ec25a570d7539653e1d793e97609adb509aaed
>
> and build that? It should be the source code for the binary VM on
> get.pharo.org.
>
F
On Sat, Apr 15, 2017 at 09:50:29AM +0200, Luke Gorrie wrote:
> On 15 April 2017 at 09:12, Alistair Grant wrote:
>
> On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote:
> > The latest stable image release is Pharo-50771.image.
> > The latest stable VM source release is pharo-v
On 15 April 2017 at 09:12, Alistair Grant wrote:
> On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote:
> > The latest stable image release is Pharo-50771.image.
> > The latest stable VM source release is pharo-vm-2016.02.18.
> > These two releases are not compatible: This interpreter (ve
On Sat, Apr 15, 2017 at 06:43:39AM +0200, Luke Gorrie wrote:
> On 14 April 2017 at 22:20, Stephane Ducasse wrote:
>
> This is what we always have when we release and we freeze it.
> The vm 60 will be compatible with latest pharo 60 image.
>
>
> It is possible that I have misunderstood
On 14 April 2017 at 22:20, Stephane Ducasse wrote:
> This is what we always have when we release and we freeze it.
> The vm 60 will be compatible with latest pharo 60 image.
>
It is possible that I have misunderstood the whole situation and there is
no problem at all. That would be awesome. Let'
This is what we always have when we release and we freeze it.
The vm 60 will be compatible with latest pharo 60 image.
On Fri, Apr 14, 2017 at 12:09 PM, Luke Gorrie wrote:
> On 14 April 2017 at 08:53, Stephane Ducasse
> wrote:
>
>> We always try to have a major release around mid/end of april
On 14 April 2017 at 08:53, Stephane Ducasse wrote:
> We always try to have a major release around mid/end of april
>
Once the dust settles, I think it would be wonderful to have this invariant:
- The latest Pharo VM source release is compatible with the latest Pharo
image.
This would make it e
We always try to have a major release around mid/end of april and this is
in addition we have pharodays + several people moving to new houses :).
And deadline for projects on top.
On Thu, Apr 13, 2017 at 12:39 PM, Luke Gorrie wrote:
> On 13 April 2017 at 12:20, Stephane Ducasse
> wrote:
>
>> We
On 13 April 2017 at 12:20, Stephane Ducasse wrote:
> We will do that.
>
Thank you! I will wait :).
Now we are under stress for the release :)
> And PharoDays. Great conference!
>
Thank you for explaining. I am new around here ("oh, are you working on a
release now?") so it helps me to have thi
Hi luke
We will do that. Now we are under stress for the release :)
And PharoDays. Great conference!
Stef
On Wed, Apr 12, 2017 at 4:57 PM, Luke Gorrie wrote:
> On 12 April 2017 at 16:43, Offray Vladimir Luna Cárdenas <
> offray.l...@mutabit.com> wrote:
>
>> I'm also interested in the upcoming N
Thanks a lot for this effort!
On Wed, Apr 12, 2017 at 4:03 PM, Alistair Grant
wrote:
> Hi Everyone,
>
> I've made a snap package for Pharo 6 which I think is far enough along
> for some wider testing.
>
> To get Pharo up and running on Ubuntu 16.04:
>
> # Install Pharo
> $ sudo snap instal
Hi Subbu,
On Wed, Apr 12, 2017 at 08:22:27PM +0530, K K Subbu wrote:
> On Wednesday 12 April 2017 07:33 PM, Alistair Grant wrote:
> >Hi Everyone,
> >
> >I've made a snap package for Pharo 6 which I think is far enough along
> >for some wider testing.
>
> Just tried it now. worked like charm.
Tha
On 12 April 2017 at 16:43, Offray Vladimir Luna Cárdenas <
offray.l...@mutabit.com> wrote:
> I'm also interested in the upcoming Nix package initiative that has been
> announced in the list recently, which also deals with installing
> dependencies in a Linux distribution neutral fashion.
>
This c
On Wednesday 12 April 2017 07:33 PM, Alistair Grant wrote:
Hi Everyone,
I've made a snap package for Pharo 6 which I think is far enough along
for some wider testing.
Just tried it now. worked like charm.
--classic - Snap packages are normally sandboxed for security
reasons.
Thanks for this Alistair. Having more self contained package options, is
good.
I'm also interested in the upcoming Nix package initiative that has been
announced in the list recently, which also deals with installing
dependencies in a Linux distribution neutral fashion.
Cheers,
Offray
On
Hi Everyone,
I've made a snap package for Pharo 6 which I think is far enough along
for some wider testing.
To get Pharo up and running on Ubuntu 16.04:
# Install Pharo
$ sudo snap install --edge pharo --classic
# If your system isn't configured for threaded heartbeat:
$ sudo pharo.config
# Down
26 matches
Mail list logo
