One Soap Box

So I figure I'd throw my desktop onto the planet like others have done already. Here's what I see when I do startx (well, close):

After I start urxvt with tmux:

Opening a browser, uzbl

The status bar at the top is xmobar and shows things that are nice to know such as memory and CPU usage, weather, the current song that's being played, the date and time, and workspace information.

• GTK theme: whatever the default is
• Icon theme: ditto
• Cursor: bluecurve (I'm not a fan of dmz)
• Wallpaper: Chosen at random every time I log in (the one shown is one of my favorites); though I have the same problem Adam has and never really get to see it.
• Launcher: dmenu with a color scheme I'm really fond of
• Workspaces: Nine; mostly used as gatherers for various tasks

and this happened. So, as this table shows, Fedora's Haskell packages aren't all that expansive at the moment. This is a list of 50 packages that I filed review requests for within the last 18 hours or so (cabal2spec and various scripts I've made make a world of difference) plus some others which have been lingering for a while (xmobar and ghc-text, for instance). If anyone would like to trade reviews, I'd be happy to do some. Also, comaintainers are welcome. Come join #fedora-haskell and we'll trade off.

Basically the result so far is that yesod is packaged as well as some other dependencies of hledger. The yesod framework which is type-safe and has a RESTful interface. No broken links, no templates throwing tracebacks, and more. The author's blog explains it better than I can if you want details. hledger on the other hand is a financial book-keeping tool which uses the same format as ledger. It has a command line and a web interface (through yesod). It can also generate charts, but if I understand correctly this is going away. Unfortunately since the current release either gets the web or doesn't it can't be properly packaged so that it can be used on the terminal without dragging yesod around. Hopefully the next version will help with that. In the mean time, there are a lot of dependencies to review.

The tools I used as two functions that I wrote to help with these large dependency chains locally. The first is lintmock which runs rpmlint over the all of the resulting RPMs from a build. This is on each of the review requests I posted (ignore the strange permissions warnings; my umask of 027 isn't liked). The second one is uprepo which takes all of the RPMs from a build and stuffs them into a local repository and runs createrepo over it to prepare it for the next build. It also splits out debuginfo and source RPMs from the others and puts each in a separate repository. You can find the source for these and some other useful functions in my .zshrc (lines 303--367 at the time of this posting).