Re: [Pharo-dev] looking for classbuilder API

2017-01-18 Thread Stephane Ducasse 
tx I will try.

On Sun, Jan 15, 2017 at 10:38 AM, Nicolai Hess 
wrote:

> maybe :
>
> newClass setFormat: self classLayout format.
>
>
> 2017-01-15 9:40 GMT+01:00 stepharong :
>
>> HI
>>
>> I need to migrate
>>
>> pvtNewSubclass
>>
>> | newClass |
>> newClass := Behavior new.
>> newClass superclass: self.
>> newClass setFormat: (ClassBuilder new computeFormat: #normal
>> instSize: 0 forSuper: self ccIndex: 0).
>> ^newClass
>>
>> and I'm looking at how to express (ClassBuilder new computeFormat:
>> #normal instSize: 0 forSuper: self ccIndex: 0).  in Pharo 60.
>>
>> Stef
>>
>>
>

Re: [Pharo-dev] ***Important*** Snapcraft pharo package for Pharo 50

2017-01-18 Thread Esteban Lorenzano 

> On 18 Jan 2017, at 13:47, Holger Freyther  wrote:
> 
> 
>> On 6 Jan 2017, at 15:07, Esteban Lorenzano  wrote:
> 
> Hi!
> 
> 
>> looks same idea of http://openbuildservice.org, I hope this is easier (I 
>> never understood how to make OBS work for us… never had the time either :( )
> 
> The pharo-vm git repository gained creating a debian source package and I 
> added auto-upload of it to OBS from travis-ci, with some extra packages 
> (libsdl2) the same can be done for Ubuntu and one could create RPM .spec 
> files (one to target multipke distributions).
> 
> What is the current state of the Opensmalltalk-vm merge? It seems to be in 
> progress and there some stability issues (e.g. unit tests are currently 
> disabled)?
> 
> Once the merge is done, tests are ran, I am happy to help using OBS to create 
> packages for various Linux distributions.

wow… this is super good, Holger, I want this since ages !

merge is done. 
there are 5 failing tests (and I still do not configure the tests for 64bits)… 
I will work a bit on this this week, but I’m finishing 3 things at the same 
time now (FFI 64bits, iceberg multi-remotes and this) so it will arrive… 
anytime soon. 

I wouldn’t wait until the tests are running :)

cheers!
Esteban

> 
> cheers
>   holger

Re: [Pharo-dev] ***Important*** Snapcraft pharo package for Pharo 50

2017-01-18 Thread Holger Freyther 

> On 6 Jan 2017, at 15:07, Esteban Lorenzano  wrote:

Hi!


> looks same idea of http://openbuildservice.org, I hope this is easier (I 
> never understood how to make OBS work for us… never had the time either :( )

The pharo-vm git repository gained creating a debian source package and I added 
auto-upload of it to OBS from travis-ci, with some extra packages (libsdl2) the 
same can be done for Ubuntu and one could create RPM .spec files (one to target 
multipke distributions).

What is the current state of the Opensmalltalk-vm merge? It seems to be in 
progress and there some stability issues (e.g. unit tests are currently 
disabled)?

Once the merge is done, tests are ran, I am happy to help using OBS to create 
packages for various Linux distributions.

cheers
holger

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

2017-01-18 Thread Guillermo Polito 
No problem ;)

BTW, you can find latest `already package` snaps in bintray here:

https://bintray.com/pharo-project/pharo/PharoVM-Snap

(Also the readme is updated)

Guille

On Wed, Jan 18, 2017 at 10:28 AM, Alistair Grant 
wrote:

> On 17 January 2017 at 00:40, Guillermo Polito 
> wrote:
> > Hi all,
> > ...
> >
> > Alistair,
> >   - thanks for the typo. Maybe we can force wget as a build dependency?
> Like
> > that it will not fail like that ;)
> >   - I'll fix the typos. However, next time could you just open a pull
> > request? or make an issue? emails tend to get lost (specially in a
> weekend
> > and with many answers :P)
>
> Sure, I'll create the pull request next time (I was a bit distracted
> and didn't even think of it :-().
>
> Thanks again,
> Alistair
>
>

Re: [Pharo-dev] [ANN] Snapcraft for Pharo

2017-01-18 Thread Alistair Grant 
On 17 January 2017 at 00:40, Guillermo Polito  wrote:
> Hi all,
> ...
>
> Alistair,
>   - thanks for the typo. Maybe we can force wget as a build dependency? Like
> that it will not fail like that ;)
>   - I'll fix the typos. However, next time could you just open a pull
> request? or make an issue? emails tend to get lost (specially in a weekend
> and with many answers :P)

Sure, I'll create the pull request next time (I was a bit distracted
and didn't even think of it :-().

Thanks again,
Alistair