A new release of Coat is available on the CPAN: Coat 0.331
It fixes a bug that appeared recently, when I added the Moose-compatible type constraint mechanism, when an undefined value was set to an attribute, it was set to 1 instead of undef.
This bug has been found by Stéphane Pontier who was experimenting with Coat::Persistent, thanks to him.
I’ve also cleaned the test-suite in order not to use Test::Exception and DateTime so the test suite can run smoothly on most systems.
It’s been a looong time since I blogged here. Perhaps I should write more frequently so you won’t start thinking I died silently ;).
I’m not dead. It’s just that I’ve started a company a couple of months ago and that does take a lot of my time. It’s pretty exciting, - as you can imagine - we’re using Debian everywhere and the team is great. I’ll write another blog-entry about that later.
In the meanwhile, I’m on holydays for a week, and I plan to squash my TODO list:
A new major release of Coat - the diet-Moose - is now available and provides support for type constraints. It’s now possible to define types, subtypes and enums as well as setting up coercions in Coat classes, in the exact same syntax as with Moose.
I’ve uploaded a new major release of TinyMCE into sid, the package jumps from the 2.x branch to the new 3.x one.
For the record, packages that use TinyMCE should rather depend on that packge instead of shipping the sources itself.
Yes I know, it’s like a year since the last development release of Backup Manager has been published, I should be ashamed of such a huge idleness.
But actually, If you ask me, I’m not. Instead of writing long lines of haiku to apologize for being so late at releasing, here is an illustrated reason why it was so loooong.
Dear lazyweb, this sunday afternoon, I opened BackupManager’s Bugzilla and started squashing bugs. There was 54 bugs opened that requested a review. 15 of them are now tagged “pending” (meaning they’re closed in SVN and will be shiped with the next release).
All of the patches submited - that made sense - were applied, thanks to all the reporters for their help, by the way.
So, fear a new release soon…
If you’re like me and want to build the ieee80211 driver for your debian box with the last kernel available in sid (2.6.24), you’ll have to apply that patch to the sources.
As you can see, a couple of changes occured in the Kernel API and that blocks the build.
Hope that can help.
Sam suggested in his lat blog entry to create a team whose role would be to handle the promotional stuff. I find that idea pretty good, having a central point where to take decisions regarding how Debian should communicate with the outside world makes sense.
I totally support that idea.
I’ve uploaded a new developer release of Coat::Persistent to the CPAN. In this version, the modules Cache::FastMmap and DBD::CSV are made optional (they were mandatory dependencies until then). Moreover, Coat::Persistent now uses DBIx::Sequence for primary keys generation.
After thinking a lot to the future of that tiny ORM (which is actually very small, unfinished and questionable) I came to a conclusion: Class:DBIx is in the place and just rules. That’s an amazing ORM and is really a great module to use. -I’m aware what follows in that blog entry may sound contradictory- I work daily with Ruby on Rails, but I just love Perl and the goodness of CPAN, I love writing Perl code, I love writing Perl modules ; I also find Rails’ORM amaizingly well designed, easy-to-use and scalable. I like the choices made, well, I like how you can feel your database through that object-mapping abstraction layer that ActiveRecord provides.
My point here is not to discuss Class::DBIx, but rather to underline how Rails’ ActiveRecord is something worth looking at, and something - I think - Perl lacks.
I may be wrong, but I feel like some Perl developers around could agree, I hope. I also hope I won’t trigger the anger of someone involved with Class::DBIx, which, let me say it again, is a great module.
My plan here is to take the ActiveRecord API, and try to upgrade Coat::Persistent, piece by piece, in order to get as close as possible to it. That’s an exciting challenge, and could give me enough intellectual food for the next months.
I may be targetting something too large for me, I may be taking the wrong path, but I feel like following the spirit of Perl taking that direction : There’s more than one way to do it, isn’t it?
At work, I was voluntold to deal with an old AIX server, and today, part of my job was to get OpenSSH up and running… Erf. How the hell could someone work with the tool “smitty”? Do they call that a package maintenance system? Do people really pay for that ?
This makes me sick, why didn’t they choose Debian? I have the strange feeling of being 10 years back in time, dealing with an old interface, user-unfriendly, terminal intolerant and anti-productive.
Sometimes, life is crual.