Subscribe to RSS Subscribe to Comments
  Save the earth NOW
earth day
Recommended resolution:1280x1024
Supported Browsers:      

Yet another open source blog ;)

Random thoughts from a Gentoo Developer

An easy way to assist us

Well, today I am gonna focus on two different types of packages. Those who never had a maintainer and those abandoned by their initial maintainers.

Looking through bugzilla, you might notice that some of the bus are assigned to maintainer-wanted herd. This means that those packages are seeking for a gentoo developer or a gentoo-user ( acting as proxy-maintainer ) to take care of them and push them on tree or Sunrise. So if you file a bug for a new ebuild, we will probably assign it to that herd and wait until somebody picks it.  Personally, I go through that list once a while and pick up interesting packages but I don’t know if the rest of the devs are in the same path. If you feel like a package is really cool and we should really have it on tree, feel free to write an ebuild for it and then commit it on Sunrise or poke me and I will commit it on tree (after we review it) and I will add you as proxy-maintainer

The maintainer-needed packages are orphan packages on tree. This is because their initial developer got bored taking care of them or because this developer has been retired. Hence nobody is taking care of them, nobody bumps them, nobody fixes the various bugs which pop up from time to time. Again, I go through that list and either remove them on behalf of treecleaner project or fix them on behalf of QA project. So the question is:

Can you help? If you file a bug on a maintainer-needed package, most likely nobody will fix it. But if you attach a patch that actually fixes the problem, then a guy from treecleaners/QA project will probably pop up and commit your patch. Congruts, you saved a package from being removed. Simple?

In order to help you,  I will give you the two URLs from gentoo bugzilla I use to track maintainer-needed and -wanted bugs

* maintainer-needed

* maintainer-wanted

Happy bug fixing

Raster to be the default Qt4 graphics engine @ Gentoo Linux

In our latest meeting[1] we decided to test and enable raster[2] use flag by default in Qt4. In order to achieve this, we kindly ask you to set this use flag on qt-gui and test as many Qt4 apps as you can. If you don’t feel like rebuilding qt-gui, you can simply append

-graphicssystem raster when launching a Qt4 application like this:

qmpdclient -graphicssystem raster

You may also post your results on the respective topic on Gentoo forums[3]

Your feedback is much appreciated.

On behalf of the Gentoo Qt team, thank you

[1] http://gitorious.org/gentoo-qt/pages/Meeting20100219

[2] http://labs.trolltech.com/blogs/2008/10/22/so-long-and-thanks-for-the-blit/

[3] http://forums.gentoo.org/viewtopic-t-816758.html

Migrating to a minimalistic desktop

Since I moved to Linux OS ( 5-6 years ago ) I use KDE as my main DE. This wasn’t a random choice, since I ‘ve tried or at least seen all the others main DEs such as xfce and Gnome. KDE is so much beautiful and convenient that I never bothered searching for something else. This is because my main activity on computers was purely based on multimedia entertainment despite the fact that I had to deal with a heavy load of University projects. Since I finished University , and dedicate most of my free time on Gentoo and other Open Source activities, I started to use more and more utilities designed for such things, such as Qt-creator, version control systems, ssh connections to various servers etc.

It is pretty clear that a eye-candy desktop enviromment couldn’t be as much beneficial as I wanted. Hence I had to search for an alternative. A minimalistic desktop or WM allowing me to take advantage of every single pixel of my 19” monitor and don’t waste them with various widgets and stuff would be ideal.

I tried fluxbox at first but I wasn’t too fond of it because it looked kinda ugly by default and I just couldn’t get along with it. So next thing to try was Openbox. I was quite surprised to see that I could tweak it and tune it up by simply editing 3 files located at ~/.config/openbox

Having created my shiny menu.xml and autostart.sh files, I emerged obconf in order to perform that last tweak on my new enviromment.

I plan to migrate my laptop to openbox as well since it looks and feel quite fast and light . Exactly what I was searching for my “tired” laptop

To conclude with, I added fluxbox-9999 and obconf-9999 packages to gentoo tree since I wanted to try the latest version of those two packages and I guess our users will like that as well.

So, enjoy :)

Refs:

Gentoo Openbox Documentation

Gentoo Openbox wiki

Ever heard of ‘proxy-maintainer’ before?

This poped up recently @ -dev ML [1]. It turns out that is little ( or not at all ) documentation about this, which is quite unfortunate since it is one of the most easy and important ways a user can use to assist us on development. A couple of months ago I blogged about Sunrise Overlay[2] as a good way for users to extend their knowledge on ebuild writting and contribute their own ebuilds on an official gentoo overlay. This of course requires a significant amount of time and effort which is hard to find nowadays.
There is another way for you to help us put your shiny ebuilds on portage. You can become proxy-maintainer of any package you like as long as it doesn’t have a Gentoo developer as maintainer.

How does this work?

Since there are no official documentation available, these are the rules you should follow to become proxy-maintainer:

1) Open a bug for your package

2) Attach your ebuild and state that you want to be proxy maintainer for this

3) Assing or CC the bug to the more appropriate herd[3]

4) Wait for a developer to pop up and accept your offer

As proxy-maintainer you should do all the required work to ensure your package is fully working and up2date. This may requires to follow upstream changes and mailing lists and visit occasionally the bugzilla to find out if there are open bugs for your package. This is an excellent opportunity to become an active member of Gentoo developer community and a big step for improving this great distro. Furthermore, you can always jump the gap and become developer[4] if you think you are willing to contribute in regular basis :)

I really hope this post will clarify this “unknown” term and motivate you to become proxy-maintainer :)

[1] http://archives.gentoo.org/gentoo-dev/msg_8c710130ea7281f9815ef84fdd2216a9.xml

[2]http://hwoarang.silverarrow.org/?p=385

[3]http://www.gentoo.org/proj/en/metastructure/herds/herds.xml

[4]http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=1&chap=2

Time to say goodbye to an old friend: Qt3

First of all, Happy new year :) . I hope 2010 to bring more joy and happiness to you and your family.

This post is a small notice for those who haven’t been informed yet about the Qt3 removal schedule on Gentoo Linux.

That’s been said, you should consider upgrade to Qt4 ( which is unlikely you haven’t already ) and upgrade your Qt3 applications to the Qt4 respective versions as well ( if possible ).

There is also a tracker on gentoo bugzilla in case you need to track the Qt3 removal progress or help us by filling related bugs ;)

Next Page »

Based on FluidityTheme Redesigned by Kaushal Sheth Sponsored by Web Hosting Bluebook. Modified by Markos