I managed to make some great progress, as you probably noticed the grub2 series is in main tree.
We still have few bugreports opened, but they are not really relevant to major usage.
The stopper issue is the lack of documentation. If you now try to install grub2 it links you to guide in my dev-space which is not really feature rich. Until this guide is somewheat feature-rich the grub2 will stay masked. So help us by filling bugs with patches to it (feel free to shamelessly steal from other wikies :))
I am also well known around by my sucking documentation skills, so don’t expect the guide magically improve from my input.
If you really care about the grub2 in gentoo just feel free to drop me mail with the doc updates, I will mostly include everything.
The planned release for libreoffice-3.5 is at February 3rd but we are preparing in gentoo right now.
I am testing up system dependencies, removing crufty addons from the ebuild and updating upstream configure.in to fit more our needs.
With all this I require some sort of assistance.
In this lovely post I shall try to describe the bumpy road that got us brand new libreoffice ebuild.
Currently we are preparing on unleashing the libreoffice 3.4 series into the calm waters of the testing land.
Release of KDE 4.7 is right around the corner and we should provide awesome experience to all czech users.In order to achieve that we need to translate lots and lots of strings.
And as the team is not so huge this is the place where you can get in the game.
So you are crazy enough to use something that use magic scripts to parse text config into another text config to make your system boot?
Good good, so lets waste some of your time and help me testing.
Lately I’ve been a bit quiet but not dead as you could see from my commit count. So lets take look on what I am up to.
This article has been rated as PG-18 due to violent behaviour and strong
language usage (I would use nudity too, but I bet you would not find my
naked pictures that amusing :)).
Wtf is this crap?
Did you ever wanted to see what keywords some package has and what overlays it is availible for you?
If you answered yes “this crap” is exactly the tool you’ve been looking for.
Idea for this tool is taken from old bash eshowkw script written by Ciaran McCreesh so kudos to him for that.
The time has come. We plan to break your systems. And as usual we need your cooperation in this. :)
So while working on all various x11 bumps I found out most misc apps does not bother to report proto header files as their dependencies.