Sorry about the ticket stuff, and thanks for the ranty review :)
Scanner is ran on postinst with a special parameter (--install) to
either upgrade/wipe the song db or to update the theme cache. It
shouldn't be needing X11 in that state, (and doesn't for me) though I
didn't try it with dpkg/apt.
If Kagu was not installed before, the postinst process should be
pretty fast since it just tries to read the db version and wipes it if
it's old, requiring kagu to run scanner on its first run.
OTOH if Kagu _was_ installed before, and the db version didn't change
(ie. upgrading from 1.0.8 to 1.0.9 it didn't) it will utilize pygame
and rebuild your artist/album imagecache. Shouldn't take more than a
few secs provided you don't use the cover art functionality. I have to
admit if you have a lot of images it will take some time. I have 180
different cover images and just timed it, takes nearly 150 seconds
(uh) for me.
Kagu features and wishlist is discussed in ITT forums (there's a
thread for each release though a little disorganized category-wise) or
in #kagu, then developers create the tickets as they see fit. But the
effing warning sign idea is good.
Thanks for your time again.
On 10/18/07, Steve Greenland <steveg at moregruel.net> wrote:
> Kagu: package maintained by Jesse Guardini. The homepage lists the
> authors as "trevarthan" and "disq". Installed from r.m.o/extras. Well,
> sort of: the postinst fails because it tries to run the scanner, which
> needs X11, which doesn't work when you're ssh'd into the N800 running
> apt-get. Not only that, it does this on upgrades as well as the initial
> install. (Digression: why am I not using the Application Manager?
> Well, besides the fact that apt-get is the One True Way, the AM is
> *slow*. And unreliable (upgrades and updates often fail, but work with
> apt-get). And there's no obvious way to upgrade packages except one
> at a time, which is both slow and tedious. End digression). There are
> two work-arounds: go to the AM, *remove* kagu, and then re-install.
> This, you will be amazed to find, is slow. The second is to edit
> /var/lib/dpkg/info/kagu.postinst and comment out the line that calls
> kagu-scanner, and then run "dpkg --configure --pending". This is much
> faster, but must be redone for each upgrade.
>
> The next step is to run the scanner, which found the oggs (recursively).
> Yea. Why is the scanner a completely separate program? I don't know.
> Why are people so enamoured of having album covers on a memory limited
> device? I don't know that, either, but at least you can disable it.
>
> Anyway, once you get past the niggly bits, it works. Well, with mogg,
> but not, AFAICT, with ogg-support. With ogg-support, it finds the oggs,
> and lists them, and says it's playing them, but no sound. The interface
> is overly fancy, to my taste, and not particularly snappy, but does
> work. (Except why can't I add an album directly to the playlist? I have
> to go to the song listing for the album. One should be able to add
> the current selection (artist, album, song) to the playlist without
> burrowing through the menus.
>
> So, long story short (too late!) I'm using kagu with the mogg libraries.
>
> Now, a quick rant at the kagu developers: you get bonus points for
> using trac, but letting your users spend their valuable time entering a
> bug report ("New Ticket", in trac language) to help *you* improve your
> product, but then rejecting the ticket as "unauthorized" is just a giant
> "Screw You" to your users. OTOH, is does keep the bug reports down.
> Either make it useful, or just disable the new ticket functionality, or
> at least post a BIG EFFING WARNING NOT TO WASTE MY TIME.
>
> Ah, now I feel better. Hey, don't complain. I told you it was a rant in
> the subject line.
>
> Regards,
> Steve
--
Kemal
