Fair point, I will make the changes.
Glad you find it useful, is there any new feature you want ?
On Mon, 6 Feb 2017 at 18:05, Sean P. DeNigris wrote:
> kilon.alios wrote
> > I see little reason to support individual pharo versions because I focus
> > always on the latest version.
>
> I'm not s
kilon.alios wrote
> I see little reason to support individual pharo versions because I focus
> always on the latest version.
I'm not suggesting that you maintain compatibility ongoingly with various
versions, but if you mark compatible versions as such in the catalog, users
won't get an unnecessar
The release what marked #common with the initial intention to make it
compatible with Squeak too since it relies only on Morphic but I never
actually bothered testing it, I have marked it #pharo now and it seems to
install fine on my end.
I see little reason to support individual pharo versions be
On Sat, Feb 04, 2017 at 03:51:43PM -0800, Sean P. DeNigris wrote:
> Ah, interesting! I wonder if this represents a bug then, because
> ChronosManager is in the metarepos for both Pharo 5 and 6, but in Pharo 5
> loads the config from the meta-repo-for-6, not 5...
ConfigOfGlorpSQLite is in both Phar
Sven Van Caekenberghe-2 wrote
> the configs must be copied into MetaRepoForPharo60, this is the way they
> are 'blessed', AFAIU.
Ah, interesting! I wonder if this represents a bug then, because
ChronosManager is in the metarepos for both Pharo 5 and 6, but in Pharo 5
loads the config from the meta
> On 4 Feb 2017, at 16:24, Sean P. DeNigris wrote:
>
> kilon.alios wrote
>> Time to make sure they work as expected.
>
> And tag them #'Pharo6.0' once it's released. In the process of loading
> ChronosManager from the Catalog in Pharo 5, I got a warning that it was not
> marked as safe (sorry I
kilon.alios wrote
> Time to make sure they work as expected.
And tag them #'Pharo6.0' once it's released. In the process of loading
ChronosManager from the Catalog in Pharo 5, I got a warning that it was not
marked as safe (sorry I forgot to tell you!). It ended up loading and
working AFAICT.
-
All my projects must be Pharo 6 ready because most of them were created
inside Pharo 6 anyway. But thanks for the reminder . Time to make sure they
work as expected.
On Fri, 3 Feb 2017 at 15:06, Sven Van Caekenberghe wrote:
> On 3 Feb 2017, at 13:48, Cyril Ferlicot D.
wrote:
>
> On 03/02/2017 1
> On 3 Feb 2017, at 13:48, Cyril Ferlicot D. wrote:
>
> On 03/02/2017 13:41, Sven Van Caekenberghe wrote:
>> Thanks for report this, Cyril, it should be fixed in version 2.8.2
>
> That was fast, thank you.
Well, the bug report was very clear, it even included the solution, and I know
I can tr
On 03/02/2017 13:41, Sven Van Caekenberghe wrote:
> Thanks for report this, Cyril, it should be fixed in version 2.8.2
>
>
That was fast, thank you.
I confirm it work now.
--
Cyril Ferlicot
http://www.synectique.eu
2 rue Jacques Prévert 01,
59650 Villeneuve d'ascq France
signature.asc
De
Thanks for report this, Cyril, it should be fixed in version 2.8.2
> On 3 Feb 2017, at 13:36, Cyril Ferlicot D. wrote:
>
> On 02/02/2017 17:18, Sven Van Caekenberghe wrote:
>> Good idea, Torsten!
>>
>> I updated the following (with new #stable releases and catalog configs for
>> Pharo 3,4,5 &
On 02/02/2017 17:18, Sven Van Caekenberghe wrote:
> Good idea, Torsten!
>
> I updated the following (with new #stable releases and catalog configs for
> Pharo 3,4,5 & 6):
>
> - NeoCSV
> - NeoJSON
> - Ston
> - ZTimestamp
> - Stamp
> - ZincHTTPComponents
> - Zodiac
> - WebSockets
> - Zinc SSO
>
>
Good idea, Torsten!
I updated the following (with new #stable releases and catalog configs for
Pharo 3,4,5 & 6):
- NeoCSV
- NeoJSON
- Ston
- ZTimestamp
- Stamp
- ZincHTTPComponents
- Zodiac
- WebSockets
- Zinc SSO
These were already running 6.0 builds on the CI servers.
Sven
> On 31 Jan 2017,
I update PolyMath for Pharo 6.0.
All tests are green: https://github.com/PolyMathOrg/PolyMath
On Tue, Jan 31, 2017 at 10:44 AM, Torsten Bergmann wrote:
> Hi,
>
> in preparation of upcoming Pharo 6 release we already should do a pass on
> all our external loadable projects:
>
> - load them into P
On Tue, Jan 31, 2017 at 10:44:04AM +0100, Torsten Bergmann wrote:
> in preparation of upcoming Pharo 6 release we already should do a pass on
> all our external loadable projects:
>
> You should do the same with your projects!
Updated ConfigOfGlorp and ConfigOfGlorpSQLite for Pharo 6. Tested on
+1
Argh I should do mine :)
Hi,
in preparation of upcoming Pharo 6 release we already should do a pass on
all our external loadable projects:
- load them into Pharo 6 to see if they could be loaded cleanly
(due to automatic transformation of deprecated messages your packages
get dirty wh
Hi,
in preparation of upcoming Pharo 6 release we already should do a pass on
all our external loadable projects:
- load them into Pharo 6 to see if they could be loaded cleanly
(due to automatic transformation of deprecated messages your packages
get dirty when converted)
- check if t
17 matches
Mail list logo
