Index ¦ Archives ¦ RSS > Tag: en

GHC upgrade

Estimated read time: 1 minutes

I just got some time to upgrade GHC to 6.10.whatever in Frugalware-current, and it seems they managed to create some screwed up bootstrap binaries, linked to lineedit. This is some BSD version of GNU readline, we did not even had it packaged and the docu says it's outdated in most distros. :-P

However, we still want to bootstrap using upstream binaries, so now we use it. At least I was able to get rid of the ugly LD_LIBRARY_PATH hack, caused by the old readline library they linked the binaries in the previous series.


Hacker Purity Test

Estimated read time: 1 minutes

I just found this test, it's an old one, almost 20 years old. It's funny to see what questions became outdated and which didn't.

Some of my favorite questions:

  • Do you complain when a "feature" you use gets fixed?
  • Ever mask an NMI?
  • Do you own more than 16 floppy disks?

Of course the last one is because I still do have more than that - though I no longer have such a reader at home - would have to go to work to read them. ;-)


Git Janitor cleanup

Estimated read time: 1 minutes

Mailed Christian Couder to cleanup up the Janitor page on the wiki a bit, since for example all the git_config_string refactoring is already done.

It's nice I did not really have to explain I do not want to destroy his work, it's just no longer necessary - he understood it just fine.


Git User Manual in PDF

Estimated read time: 1 minutes

I just sent out a patch to add support for generating the pdf version of the git user manual. I (and some of the guys at the uni - just discussed recently) prefer reading long docs in pdf, rather than in the memory leaker firefox.

We'll see how it'll be accepted.


Enjoying search autosizer

Estimated read time: 2 minutes

This was getting more and more annoying. So my problem was that whenever I searched for something in Firefox, I typed it to the search bar and the query was left visible there. This is just totally idiotic for (at least) two reasons.

First, those search queries show what you are thinking about. It's normal that you don't always speak about what you are thinking about, so why would it be logical to always show what are you searching for. This is just uncomfortable for other people, they come to your box (somebody from the family, etc), want to search for something and they see what you were searching for, and they will think about "why did he search for this" - not that they care about it, they just don't want to see this info.

Second, I regularly work in a library and such places where the contents of a query may be just sensitive info and/or NSFW.

OK, so as the result of the previous problems, I saw myself just hitting enter in the search box to get the normal search form and search there so the original search box remained empty. This was abnormal.

Today I spent some time searching for a proper solution for this and sort-of found it: the Searchbar Autosizer extension. Actually it's stupid as it re-sizes your search box (so make sure you remember the size of it before you install this extension), but you can make it a fixed value again and in the second dialog of the preference wizard you have the option to clear the search box right after you hit enter. Excellent, that's what I was looking for. :)


Fast distributed development

Estimated read time: 1 minutes

So when I first sent a kernel patch to the x86 subtree, I had to wait a lot. The patch (commit 273c112 in linux-2.6.git) was created in May and the first release (v2.6.27) was out in October. Then I discovered that critical bugfixes and security fixes are a different matter, getting such a patch in a release takes 1-2 weeks, depending on the priority of the patch.

Today I noticed that the newest git release (v1.6.0.5) comes with my patch which I just created 1.5 days ago. Yes. that's how does goes if people know you. :) OK, this is not a rule, a release may take more time, but it is really committed in ~2 days in most cases - if the patch itself is correct and you earned some credit already from the maintainer.


Export to C from Gimp

Estimated read time: 1 minutes

I like this feature. It's pretty useful now when I have a homework at the uni where the whole solution should be a single C file. So I just do a texture in Gimp, export it to C, copy&paste it to "the" file, and stop wasting my time trying to create some texture by hand. Yay! :)

Having fun with boost 1.37.0

Estimated read time: 1 minutes

So we decided to upgrade from 1.35.0 to 1.37.0 in Frugalware-current. As usual, there is a WIP repo since this won't be finished in one day. Most of the trivial rebuilds are done, but still need to fix up miro, pdfedit and bmpx. Ah and I needed to upgrade libtorrent as well which resulted some problem in btg and qtorrent, though both have some support for the new 0.14.x libtorrent in SVN so most of the work was just to backport those patches.

A user on #frugalware asks when will we have python-2.6. Not before boost-1.37, I'm sure.

Side note: It seems I managed not to waste the whole day just because I met and old friend (and drinking beer). It turns out that if I drink 2 beers and sleep 2 hours then I can code without the usual "go to bed early, sleep a lot, then you can work" procedure.


kernel.org gitweb fork

Estimated read time: 1 minutes

It has not been updated for a long time, but today a fix appeared. It seem to be kernel.org-specific though, so don't worry.

gitte on tailor

Estimated read time: 1 minutes

Today evening gitte collected a summary of his tailor problems, which I would call a nice collection.

He says:

01:31 < gitte> vmiklos: tailor was limited in many ways.
01:31 < gitte> vmiklos: one, basically branch per branch.
01:32 < gitte> vmiklos: two, it was written in Python
01:33 < gitte> vmiklos: three, it did not define a language, but a
                     class interface
01:33 < gitte> vmiklos: four, it made assumptions about the internal
                     organization of SCMs
01:33 < gitte> vmiklos: five, it is maintained in a darcs repository,
                     which tailor cannot even convert to Git.
01:35 < gitte> vmiklos: oh, and it did not help that the configuration
                     is awkward and badly documented, not to mention
                     inconsistent with regard to the types of input/output
                     repositories.

© Miklos Vajna. Built using Pelican. Theme by Giulio Fidente on github.