If something isn’t clear, mail me. If you know how to explain some things better than I do, or you’ve spotted a misspelling – mail me also. My english sucks and I wish I could make the reference better somehow. Also if you want to translate it or do something else with it – feel free to do it, I don’t care about any kind of copyrights here.

I had integrated the bmpanel2cfg into the build system yesterday and now I’ve returned the previous build chain for man page. In order to build man page properly you need to have asciidoc package and docbook-xsl stylesheets. Currently CMake build script tries to detect the a2x tool and if it’s here then tries to build the man page. A2x toolchain manager is a part of the asciidoc package usually and in the archlinux for example asciidoc depends on the docbook-xsl package too, so.. everything should be ok here. But I have no idea how it will work in other linux distributions. If you have any problems – mail me.

P.S. Even though writing a comment on the blog seems like a faster way to give your feedback to me. It’s actually not. WordPress spam filter often sucks up your comments and I don’t get any mail notifications in that case. I check spammed messages rarely. So.. really.. if you have something to ask – mail me. Fortunatelly, the gmail has the best spam filter I’ve ever seen and it hardly ever puts important mail in a spam folder.

Recently I’ve been working on bmpanel2cfg integration into cmake build chain. And it looks like everything works now. If CMake sees the python interpreter it will install the bmpanel2cfg script along with bmpanel2. DESTDIR should work too. But if you’re packaging bmpanel2 and encountering some problems with that, please let me now.

Actually there are very few things left before I will make the 2.1 release. I think the project has accumulated a lot of changes and it’s time to make a fresh release. But before that I need to:

Fill “black spots” in the documentation area (theme reference and bmpanel2rc(!)).

Decide what themes should be included in the next tarball release. I don’t like them all equally, some of them will get into, some of them won’t.

Prepare a big changes list (2.0 to 2.1).

And couple of other minor things, which you’ll never notice probably anyway.

As you may have noticed, the wiki pages on the code.google.com site are gone. It’s the result of me trying to make a Mercurial mirror for bmpanel2. But apparently code.google.com totally can’t do wiki repository conversions. So.. There is a big mess. I’m trying to get over those bugs, but currently I can’t do anything about it.

Btw, the contents of wiki pages are saved. Probably all this may result in a project hosting migration. I’m really disappointed about code.google.com. The *only* thing I like there is the bug tracker.

UPDATE: The wiki is back.. 😛 But comments are lost, sorry for that. I think it’s not critical.