- The meta/Recipes script doesn't run the post-install of debian
packages, so some weren't installed correctly.
- This scheme lets vigil install into a container as usual.
- The files in the AppDir are calculated as the difference between
the files in the initial debootstrapped container, and the
container after the installation.
- It wasn't worth the complexity. It was only useful when running the
python profile tool, which executes python scripts. But that tool
isn't very useful when run against normal scripts. It has been
removed too.
- The sandbox also wasn't working inside snaps, appimages,
systemd-nspawn or chroots.
Putting the statuses on the left and the paths on the right
works better when the window is narrow, because the paths were
often invisible when on the left.
- Now using python3.4 on debian, and python3.5 elsewhere.
- Added test-distributions script that checks that
install-dependencies works on different distributions.
This had stopped working.
Unfortunately it doesn't seem to help anyway.
Ideally the responsiveness of the interface is the same, regardless
of whether the workers are paused or not. Atm its much better when
they are paused.
When I tried this before threading was working better.
Now asyncio is doing better.
Recently, exceptions were happening occasionaly in the update
thread. I guess due to races. They should go away now.
From now on, if a coroutine takes too long the interface will hitch.
Should investigate if sync_to_filesystem is taking too long and
if it can yield.
There are no uses of threading now.
I was having problems with the old scheme.
Now you use tab to switch focus between the summary and result
panes. The keys to navigate are the same in both places.
