Muon Suite 1.4.1 released

I am glad to announce the first bugfix release for Muon Suite 1.4. The Muon Suite is a set of package management utilities for Debian-based Linux distributions built on KDE technologies. Sorry that this is a bit late. I meant to do this two weeks ago, but my MBR died that weekend. That got fixed, but I’ve not had a chance to do this release until now…

The 1.4.1 release fixes several issues with the experimental Muon Discover frontend. Additionally, a bug where the Muon Notifier would hang KDED for 25 seconds when checking for new versions of Kubuntu was fixed. (Only affected people behind system-wide proxies)

Packages for Kubuntu 12.04 are from the QApt repository, and in the main repositories for Kubuntu 12.10.

Further technical information about the release, including source tarball downloads and a detailed changelog, can be found at the project pages here and here.

Exciting things are happening in Git, so stay tuned for some blogs on that in the near future! (Maybe in two weeks or so?)

3 Responses to Muon Suite 1.4.1 released

  1. Random says:

    How difficult should be porting Muon to PackageKit?

    • Fairly difficult. (And we’d be talking about the Muon Software Center/Muon Discover only, the Package Manager and Update Manager would require rewrites, basically.) There are many things that APT can do extremely quickly that Muon assumes can be done synchronously. (E.g. get the name of an arbitrary package.)

      With PackageKit, *everything* (e.g. info on local packages) has to be acquired by making a D-Bus request to the PackageKit daemon, and therefore must be done asynchronously to prevent freezing the client application while waiting for a response.

      So I guess it’d actually be pretty easy to make something that *worked*, you’d just probably see freezes in Muon while waiting for your D-Bus response from PackageKit. It wouldn’t be too great of an experience. (Which is why I created LibQApt and Muon in the first place)

  2. Greg Pitta says:

    Sorry, hit enter before the example, suppose I installed a program along a lot of dependencies one month ago. I remember the program and I want to purge all of its dependencies, I could go to history search for the program and mark from the history panel to purge/remove it along all the packages installed at that day at that time.

    I would find this an useful feature, hope the I got to explain the idea well enough.

    so, thanks again for your work,
    Best Regards
    Greg Pitta

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: