So now that the slashdot effect is wearing off for good I can consider the migration with a lighter heart. I’ve tried blojsom, and I have to say I’m impressed by its speed; unfortunately I was able only to enable textile on the posts by adding keys directly on the database, which is not really that good, and I haven’t found how to enable per-category feeds; the documentation on the official wiki seems to be still referring to blojsom 2.x rather than 3.x.
So last night I’ve started looking at the installation documentation of Roller that, beside being used by Sun and IBM, is going to be part of Apache project, if I read thhe page correctly, so something good it has to have 🙂
Unfortunately the main problem here are the dependencies, as it requires quite a bit of symlinks, as it needs Hibernate, that I had to ask the Java team to bump in portage, as it was a bit outdated there 🙂
So I’m now trying to merge all the dependencies of it on Prakesh to see how many needs to be migrated and how many I can easily keyword 🙂 At least two packages are currently fetch restricted, but it’s not that big of a problem unless they package ELF binaries too (which I sincerely hope they don’t).
Of course, I’ll have to rewrite again the conversion script, as obviously the one I wrote for typo to blojsom conversion won’t work, but that is not really a big problem to me as also Roller’s database seems to have a decent schema, for sure better than Typo’s.
Now, I wish to thank all the people who supported me, and who said hoped I’d be reconsidering my leave in the next months while I finish my tasks, but just while I was writing this blog entry, the last straw made me snap, so I’m leaving, today. Why this? Because really, you have to want me to die if you ask me to rewrite autotools.eclass every time I’m asked to change its behaviour! Good Lord, I was asked to change the behaviour of autotools.eclass to default to latest (see gentoo-dev thread) and now I’m told I should have rewritten the code not to check the variable twice ?! I would have rewritten the code anyway as soon as mips stabled automake-wrapper (that should have happened in a few days anyway), so why should I change the code to make it prettier if it only lasted a few days? Why not doing the logical thing of changing the minimal part of the code to add the new default behaviour (that IMHO is still wrong)? And what am I told by other devs? To calm down? I was still with my AFK nick, because today I wasn’t planning on being around for long anyway, beside tonight (when I won’t be, as I left the task to UberLord).
So, good luck people, I now wonder who needs more.
You’ll be missed man, you’re a really good developer, and I’d said to myself, in the face of all the devs leaving “I’ll keep using Gentoo as long as Flameeyes does.”I think you leaving is just yet another sign that Gentoo will die unless they change, and that’s why I’m now on Arch Linux (for a while at least 😉 )
This is a sad day indeed. )-: I’ve always admired your work since I started reading Planet. Respect to you for putting up with all the crap for so long.
I am grateful for all the hard work you’ve put into Gentoo. It’s a shame that a talented developer like you was forced to leave the project. I was hoping that you would reconsidered your decision, but I respect your choice and wish you luck.
A sad day indeed, although I fail to understand the exact reason that made you quit immediately.Anyway, I’ve had great pleasure reading your posts on planet.gentoo.org. So thanks for all those interesting posts and all the hard work that you have been doing. You will obviously be missed.I hope we will see your contribution in other OS-projects in the future.
re autotools.eclass – you can always just say, “No” to whoever asked you to rewrite it. Being a Gentoo dev is about doing the stuff _you_ want to do, not what other people want you to do.
A sad day, indeed. I really start to wonder, how long Gentoo can stand the current average of good devs leaving.Thank you very much for all the great work you did for Gentoo. Good luck in whatever you plan to do next.