So now that 2.0 is out of the door, i can start development again. The freeze was long and cold. Apparently, during the freeze, some fairly nasty bugs went unnoticed for ages. The java and flash user interaction not quite working are among the more annoying. More of a problem is that i currently have no idea what the problem is or how to fix it. Dialog debconf frontend works just fine on my debian system under adept. But well, they are both non-free, so that makes the problem not too severe. If i figure out what’s the problem i’ll fix it.
In the meantime, i have started working on adept 2.x. The first one will be 2.1, which brings renaming of the source package to adept, renaming the libept subdir to “adept” to be consistent with other libs (so you have #include ), rename the ept namespace to adept, split up the debian package. The user visible change is that adept apps now show GUI much earlier on, showing a “loading, please wait…” message. Previously, the GUI would only appear after a lot of processing so it could seem that the app failed to start and anxious users would try to run it again or something.
As for my plans for summer. I want to work on libapt-front (now libept) 0.4. For the shorter term, i want to make adept much more reliable with dpkg/debconf handling. It now mostly relies on the distro to make everything smooth. And this doesn’t quite work with development branches. For longer term, adding (some?) support for additional metadata (changelogs, news files, whatever the debian package metadata project comes up with). And another important step would be adding support for apt-rpm and porting adept to fedora core. If this works out, i’ll try to include it in fedora extras. Since apt-rpm now supports repomd and multiarch, adept has a chance to become a full-fledged package management suite on rpm platforms as well. World domination. Hah.