So, what’s cooking inside Sabayon and inside my life?
First of all, I am happy to announce that I am close to extend my contract with Weswit, if you don’t know who is it about. It’s a Web3.0 company (XD) producing the Award winning multi-platform Real-Time data transmission Server called Lightstreamer. I’m having an outstanding experience there, learning new things every day, fighting against the most bloody bastard bugs you can ever imagine, where data concurrency is the standard. So, things are going really well on this side.
At the same time, I’ve been busy with the damn university stuff, studying really tedious things, like Probability and Statistics, sucking all my time. I hope to graduate in a year and a half, depending on business opportunities (and my laziness). I’m also planning to do the internship next year, hopefully at Google (if I’ll pass the tricky tests) or somewhere else, who knows.
On the Sabayon side, 3 main things to report:
- Sabayon Gaming Edition. Christmas is coming, and so our Gaming Edition, can you imagine, a Sabayon DVD full of wonderful Linux games? Unfortunately, there aren’t many commercial games around, so their demos (hoping to see things changing with the introduction of Chrome OS), but still, we can show the world that Linux is a valuable, performant Gaming platform when the whole Graphics stack works (fglrx and nvidia drivers aren’t that bad, with the latter being as performant as in Windows).
- Website. We’re planning a migration to Drupal, moving the Entropy part to a separate subdomain, hoping to make it easier to keep in sync with the rest of the coolness around (skins mainly). ETA: Spring 2011, hopefully. If you can help out, mail us.
- Entropy. Conditional dependencies ( ( app-foo/foo & foo-bar/baz ) | new-baz/bar ) support. Binary packages delta downloads (almost implemented, just missing client-side code). Integrated anti-rootkit functionalities (equo security oscheck). Reworked the configuration files syntax, keeping backward compatibility. And a lot of other bug fixes, speed improvements and API refactoring. The next big thing will be mitigating the effects of corrupted filesystem on a sqlite3 database (sqlite3 db is used for storing repository metadata).