Now if you double click on a rpm/deb file you will get the following UI:
localinstall auth dialog
You always get asked for the admin (or user) password so that this can't be abused by a malicious script when you have asked PolicyKit to remember your password.
We're a couple of weeks from the release of 0.1.0. There are no DBUS API changes planned in the near future, and we're just going though the list of blockers for release.
Join us in #PackageKit on freenode if you get stuck or you want to ask any questions. Thanks.
Today I stumbled on the following blog post – basically, it's a developer from gentoo saying that because PackageKit won't ask the user for compile flags it's unsuitable for use in gentoo. The author then goes on to define an overly complex abstraction for package management suitable for gentoo.
I appreciate gentoo is not a “install epiphany” type distro, more a “configure firefox with libxml and libsvg” type distro. That's fine; choice is a great thing, but I don't think implementing yet another abstraction is going to work for a distro like that.
And then I found the following IRC log about frugalware, also doing the same with a frugalware specific gfpm. Really, some of these frugalware guys need to be hit with a big clue stick – read the IRC log and see what I mean. They don't want to ship pam, or PolicyKit, or any software install tool that “depend(s) on any external software like dbus”. Indeed.
I've just been sent a new design proposal for the pk-prefs dialog:
It's a lot more concise, and seems to represent the relationship between the sections better. I like it. Comments?
I want to download updates in the background. Does Linux have the equivalent of WIN32 BITS? BITS is a Background Intelligent Transfer Service used for downloading Windows updates in spare, low priority bandwidth.
When I do an automatic daily update yum saturates my bandwidth for a couple of minutes which makes browsing really slow. Is there a way of throttling the yum download with Linux? Thanks.
A pretty-useless debugging client for PackageKit I wrote in a few minutes:
Useful to PackageKit Hackers…
It basically allows you to see what the currently running backend can do, and what is left to implement. Some of the backends can't do all the actions, so this tool can show you what they should be able to do. It's not pretty, but it's for programmers, not end users.
Currently the name of the package management tool is “Manage Packages” in the GNOME menu. It's a way of searching for and installing or removing software in a fairly techy way. Fedora name the pirut tool “Add/Remove Software” and I'm sure other distros name the “installer” different things like “Software Installer”.
The update viewer is currently called “Update Viewer” as it's primarily a way of seeing what changed and the reason why, rather than a way to apply the updates (although it can be used to trigger that too).
As usual, I've currently chosen rubbish names….
I need some help on the menu names of these applications – some suggestions:
Package Update Viewer
Software Update Viewer
View System Updates
In the future there will also be a tool “Application Installer” that just has a list of common applications like “Pidgin” and “Abiword” and ratings and that sort of thing. This requires integration with the online desktop thing and needs some fleshing out from a design point of view before any code is written. I want to get the “system” tools written before I flesh out this idea.
Other name suggestions welcome, as usual. Reply via blog or email. Thanks.
David posted a comment to my last blog entry with a sarcastic “What is a cache and why do I need to refresh it?”. He's got a valid point.
To me, having “refreshing a cache” in the status UI is much like the rationale for having both suspend and hibernate in the UI. The user shouldn't need to know the difference between suspend and hibernate as they are both ways of making the computer “sleep”. The reason why we have to expose both into the UI is that suspend is fast, but has volatility, and hibernate is slow but doesn't. This is just a technical design decision that is made due to other unfixable design decisions or hardware limitations.
I think it's much the same for refreshing a cache. The user shouldn't have to know what it is doing, it should just work, but the unfortunate drawback is that refreshing a cache can take quite a long time and during that time none of the other functionality like searching or getting the update list works until this is completed.
So, the short answer is that the cache is automatically updated on the first logon (20 seconds after the network comes up for the first time) and then every 12 hours after that. It will be per-session configurable in gconf for sure (as you don't want to suck 500k of metadata down a 14k dial up link….), and you can also force a refresh in the update GUI tool.
I welcome other more less-technical names for “Refreshing package cache” maybe:
- Updating package lists
- Updating software metadata
- Refreshing repository data
Other name suggestions welcome. Reply via blog or email. Thanks.
I've just completed a big entry off the TODO: queuing transactions that can't be done in parallel. This means you can do RefreshCache and then GetUpdates straight away, and the latter will wait (async of course) for the first to finish. Before we just failed the second transaction which wasn't very nice. Also, when it's sane to do so, we run all queries (that don't write to the disk) in parallel with other tasks.
Grammar, yadda, yadda
The code is lightly tested, but seems to work okay for me. This was a bit of code that I had put off writing for a few weeks as it was always going to be tricky to do right.
There's also code in the daemon now to log transactions to the database that have potentially changed things. This is the first chunk of code needed for the rollback support for some backends, and also allows us to find out “what was updated yesterday because now java doesn't work”.
So basically what I'm trying to say is that there is lots of new code in git today, so expect it to break horribly. Please yell on the list if you find anything odd.
Well, hacking is going good. New backends are being developed and merged, and the underlying daemon is a lot more stable. There are now helpers for threaded backends, so in theory they are as easy to write as the external spawned backends. I've merged lots of patches this weekend, and only have two more things on the “complete before first release” list.
| conary | yum | apt | box | alpm | ----------------------------------------------------- refresh-cache | X | X | X | X | | get-updates | X | X | | X | | update-system | | X | | | | search-name | X | X | X | X | X | search-details | | X | X | X | | search-file | | X | X | X | | search-group | | | | | | install | | X | | X | X | remove | | X | | X | X | get-depends | | X | | | | get-requires | | | | | | get-description | X | X | X | X | | get-update-detail | | | | | |
So, all being good, I hope to release version 0.1.0 in the next few weeks.