On 26 December 2017 at 01:51, Hilaire <[email protected]> wrote: > Let's discuss it in another thread. > > Until now, I moved slowly to update the drgeo build script to adjust to > Tonel file repository and P7; mostly done now. Will now look for help from > Pavel to build the drgeo image from a tiny core. > > About the other problems to get a user ready drgeo application based on > the forthcoming P7: > > - set up an application 64bits VMs architecture for Linux, OS X and > Windows (aka one-click image). I understand the later may be a problem as > there is not yet 64bits VMs. > > - get over the strange oddities appearing with P7, long and tedious but > mandatory; otherwise this sets back drgeo as an end user (student, > teacher) will immediately run away if drgeo is unpredictable. It really > took me a long time to get drgeo right on P3 because these oddities only > show up at runtime, under specific scenario. There are easy to fix, > thought. Writing more tests should help too. >
It would be great to have Issues opened with new tests attached for these specific cases that currently fail which we can work on make green. They make the problem nicely explicit to work on. cheers -ben > > Hilaire > > > Le 25/12/2017 à 15:57, Stephane Ducasse a écrit : > >> 5. fulfill the promise of tiny image, aka bootstrap and 4. >>> >> Did you see that pavel produced a smaller image than the first >> bootstrapped version >> >> All these wishes are under construction, so likely to happen \o/ >>> >>> >>> I have personal three wishes (beside good health of course), sharing it >>> in >>> case others are interested to hack on it too: >>> >>> A. get DrGeo working on P7, particularly on the bootstrap process. >>> >> Let us know the problem you face because this is important that you can. >> >> >> > -- > Dr. Geo > http://drgeo.eu > > > >
