QApt sexiness…

…or shrinking your GRUB list the easy way!

/Going into [K]Ubuntu mode…

Have you ever seen your GRUB list grow into such a monster?

Wouldn’t it be great if you could bring it down to this?

The Easter Bunny has the solution:

Simply select your old/unwanted entries and BANG, gone! Can’t get any simpler than this!

Boring details follow (that is, no more eye candy screenshots).

I am talking of course about kcm-grub2, the GRUB2 Bootloader Editor. On Git (soon to be released, perhaps in a week) you can find package management integration in this GRUB KConfigModule which enables you to easily get rid of old GRUB entries the easy way (TM), without having to search in package managers about the packages you would normally have to remove in order to make your GRUB list smaller.

And all of this thanks to LibQApt and Jonathan. Kudos for an excellent package management API which allows anyone to do such sexy things for KDE.

/Going out of [K]Ubuntu mode…

PS: Obviously this feature can be used only by [K]Ubuntu users (once released of course). This feature was tested in Kubuntu Maverick Meerkat. Other xUbuntu distributions are expected to work, including Debian. Theoretically, any distribution where libqapt is available should work. Hope that clarifies things a bit.

34 thoughts on “QApt sexiness…

  1. Pingback: KCM-GRUB2支持卸载旧的linux内核 | I, KDE

  2. > PS: Obviously this feature can be used only by [K]Ubuntu users (once released of course).

    Because you are planning to patch the Kubuntu packages and not submit upstream or because only *buntu uses the .deb packages?

    • It was my bad actually. LibQApt is currently packaged only for Ubuntu (there is ongoing work with packaging for Debian), that’s why I was talking mostly about [K]Ubuntu. I don’t really expect users to manually compile LibQApt and then kcm-grub2 just to get this feature, we heavily rely on distribution packages.

      • Wait, you don’t expect someone running stock Debian to be compiling interesting packages on their own? Maybe LibQApt and kcm-grub2 have some nasty dependencies I don’t know about, but failing that let me assure you that the average Debian user is not to be dissuaded by the need to compile😉 (and they can always use checkinstall to do it The Debian Way).

        • The target audience of a GRUB2 Editor is mostly newbie users. Any user capable of compiling kcm-grub2 almost certainly can hack on his own on the GRUB configuration files. Quite often advanced users frown upon a GUI for editing GRUB actually, because “you miss all the Linux magic” etc.

          I never doubted that the average Debian user can compile something on his own, but experience shows that binary packages make [average] users happier than source code🙂

  3. WOA! Nice! justr yesterday i removed 20+(!) old kernels. i dont understand why they are not removed automatical maybe with an “max 3 old kernel versions”-strategy. however. with your solution, now its a childplay. big thanks.
    p.s. kubuntu ftw! xD

    • I second that. It should not be too difficult to set a limit? Actually, I think this should be a part of the standard KDE package. Anything that can make life easier for users should get in there.

      • To get this behaviour automatically (that is, whenever kernels are added/removed) it would require an external script. Up to now this behaviour used to be controlled by distros, not upstream by KDE. I’ll have to ponder a little over this and if I find a viable solution I will add it to this GRUB Editor.

  4. Pingback: KDM supporta le opzioni di GRUB2 per riavviare il sistema da KDE 4.7 | Follia Digitale

  5. Pingback: KDM supporta le opzioni di GRUB2 per riavviare il sistema da KDE 4.7 | CorryL's Blog

  6. Isn‘t qapt also that tool that totally unintuitively lets you manage your deb repositories? Which is totally annoying with thousands of dialogs that are totally pointless such as (“All packages have been updated”) that steal focus and that cannot be closed using the Esc key and that block everything?

    • No, not really, it won’t get in the way if that’s what concerns you. You only get a confirmation dialog before removing the packages, that’s all. You may be referring to Muon, the package manager built on top of LibQApt, but this has nothing to do with this GRUB2 Editor, other than that they use the same library.

  7. Pingback: KDM supporta le opzioni di GRUB2 per riavviare il sistema da KDE 4.7 | Indipedia – Indipendenti nella rete

  8. Pingback: Links 25/4/2011: GNOME 3 Live Image 1.1.0 Released, US Army Chooses Android | Techrights

  9. Nice work, but I think the dialog box for removing entries could be slightly confusing for some users as it isn’t obvious that the ticked entries will be removed, people might think that the ones with ticks will be kept. Just putting a label at the top with “Select entries to remove:” would help a lot.

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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 )

Google+ photo

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

Connecting to %s