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 because I focus always on the latest version. Ephestos projects like ChronosManager are made for personal reasons and are not intended for public consumption though I encourage it I do not have the time or motivation to make it work well for everyone. Including supporting older Pharo versions. On Sat, Feb 4, 2017 at 6:00 PM Sven Van Caekenberghe <[email protected]> wrote: > > > On 4 Feb 2017, at 16:24, Sean P. DeNigris <[email protected]> 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 forgot to tell you!). It ended up loading and > > working AFAICT. > > Euh, no, the configs must be copied into MetaRepoForPharo60, this is the > way they are 'blessed', AFAIU. > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Pharo-6-update-catalog-entries-tp4932354p4932978.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > >
