> On 25 Nov 2014, at 23:39, Nicolai Hess <[email protected]> wrote: > > > > 2014-11-24 23:34 GMT+01:00 Esteban Lorenzano <[email protected] > <mailto:[email protected]>>: > both are integrated into the image. > while NB has been maintained directly, athens should still be loadable (if > not the case… we have a problem for the future :P). > > what does that mean for athens, yes unload and loadable from the image or > loadable from the sthub repository?
no idea… I guess is the same case, but I have no control over that area. Igor will know better :) Esteban > > > > yes, we are slowly moving in the opposite direction of “all maintained in the > image”, and eventually we plan/dream to have a small kernel and a bunch of > configurations to produce Pharo. > > now, about NB, we do not have special plans. > it is in the image and it will be maintained as part of Pharo. > > now, since the most common use of NB is for FFI, and NB is not present in all > platforms, we are working (Ronie, in this case) in a “unified FFI”, which > will provide a common abstraction layer for several FFI frameworks (NB, > OldFFI, Alien…). With that, we can choose which one of the frameworks we use > depending on the situation (but ideally, we will maintain just one, the one > that fits better in Pharo). > Again… this are just ideas for the future :) > > Esteban > > > >> On 24 Nov 2014, at 23:23, Nicolai Hess <[email protected] >> <mailto:[email protected]>> wrote: >> >> 2014-11-24 20:41 GMT+01:00 Torsten Bergmann <[email protected] >> <mailto:[email protected]>>: >> Hi, >> >> were is NB currently maintained? Only within the image as it is integrated >> or still with an external config and on STHub? >> >> The reason why I ask: when I load the latest NB-Core package >> from STHub it looks like this one is outdated and back from Pharo3 day >> (trying to load it gives problems from changes in Pharo 4). >> >> So it looks like NB was originally developed external using STHub, then >> integrated >> into standard image and now it is only internally in-image managed. OK. >> >> But the future goal is as far as I understood to manage more and >> more packages using external configs again. >> >> What is the status and future plan for NB? Will the repo get >> synchronized? Or will it stay internal only? >> >> Thx >> T. >> >> >> I was about to ask the same question for Athens, the packages in pharo4 and >> sthub diverge. >> I can merge the sthub and pharo4 version for Athens (and mabe NB), I just >> don't know what >> is the plan for the feauture, manage packages for Athens and NB in the image >> or on sthub. >> > >
