Orphaned packages
Orphaned ( aka maintainer-needed ) packages, are those that nobody, neither a maintainer nor a herd, is looking after them. Such packages oftet get removed from portage because either they don’t work anymore or there are just too many open bugs and nobody really cares about them.
Recently the TreeCleaner Project, as a decent way to inform everybody ( both devs and users ) about packages that are candidates for removal, introduced a new package to track them.
http://www.gentoo.org/proj/en/qa/treecleaners/maintainer-needed.xml
If you want to proxy maintain one of them, just send an e-mail to gentoo-dev mailing list and who knows, maybe a dev will pop up and work with you :-). If you haven’t heard about proxy maintainers before just take a look here and here.
Halevt: A replacement for ivman
It’s been a while since kargig and I worked together to bring sys-apps/halevt to Gentoo portage tree. To be honest, I didn’t quite use it, since all of my PCs where configured to use ivman, so I was too lazy to do any changes. However, due to the upcoming removal of ivman, I decided to migrate all of my PCs to halevt. The migration was quite smooth except a minor ( or major, depends on your point of view ) issue; Removal devices such us USB disks or external HDDs, were mounted just fine, but regular users didn’t have write access to them. Digging around, I found this post on Gentoo forums. What I had to do was to replace every
exec=”halevt-mount -u $hal.udi$ -o sync -m 002″
to
exec=”halevt-mount -s”
It seems to me that the default conf file that gets installed with halevt is rather useless for normal users because they are unable to write on external devices. If you feel like I should ship another configuration file, optimized for your needs, I am willing to hear your suggestions and come up with a rather convenient file :)
Why should a package respect LDFLAGS anyway
Following my last post about Gentoo QA and Diego’s one , I will try to explain why this QA issue is that important. As you already know, the Gentoo Council decided to add -Wl,–as-needed to default LDFLAGS. If you don’t know what does this mean, you may want to read this article from the QA documentation. However looking at this traker, I see more than 90 bugs not respecting LDFLAGS at all. Can you see any *doh* here? Yeah thats right. While the move towards -Wl,–as-needed addition to LDFLAGS is a big step forward, the tree is not ready for this just yet. Thanks to Diego’s tinderbox for filling all those bugs, we are now able to fix these packages once and for all.
Recently, a discussion took place on gentoo-dev ML about this issue and as it turned out, few developers didn’t actually know how to track packages that don’t respect LDFLAGS. One way is to read the build system or just observe the output during build time. Another decent way is to add –Wl,–hash-style=gnu to default LDFLAGS. This is how it works: The hash-style ( in our case GNU ) ends up in the final binary. If portage can’t find it there, it simply means that the ldflags where just ignored ( Thanks to Samuli for the explanation ). More info about –hash-style can be found on ld man page.
For our fellow Arch Testers, amd64/x86 pages[1][2] have just been updated to include this piece of information, so unless you want to use my QA powerzz against you, simply adjust your LDFLAGS before you perform any kind of testing.
Update (24/8/2010):
-Wl,–hash-style=gnu is now default on linux/amd64/10.0/developer profile. Lets see if this help us spot more broken packages
[1]http://www.gentoo.org/proj/en/base/x86/arch-testers-faq.xml
[2]http://www.gentoo.org/proj/en/base/amd64/at/index.xml
Summer Vacations: Molyvos
This summer I chose a more quiet place for my vacations. I visited Molyvos, a traditional village located at the very north side of Lesvos island. 2,5 hours away ( on boat ) from my small town, seemed like an excellent choice for this summer. See what I mean :-)
Beer
Before..
After…
The Castle
The Port:
Yeah, so Greece is not just Mykonos ;)


















