So I received my first patch for Perl code a week ago. Amazingly I didn’t have to tell the person patches were welcome, they must have assumed so because my project was licensed under an OSI approved license. Also amazingly I’ve applied the patch even though it didn’t meet my quality standards. I figure that’s my fault though because no where did I document what those were.Back when I forked Regen2 from Funtoo one of the first things I did (and a reason for the fork) was create a policy for patch submission.

So I’ve decided to “compete” in the Iron Man competition.My name is Caleb Cushing, I’m a 25 year old, unemployed, student, living in the Greater Lansing, MI, USA, area. I’ve been programming perl for approximately 6 months. This includes a lot of off time, time to relearn the language from the class I took a couple years ago (and learn modern perl), learning Catalyst and DBIC, all of which is an ongoing process.

as I’ve been saying here recently I’m burned out, on so many angles it’s not funny. I’m apathetic, I’m not really sure I care anymore. I’m actually playing with arch at the moment to see if it’s a better fit. I also here debian sid might work. I don’t want to maintain the tree 7 days a week anymore, and I’d like an up to date system. I’ve been talking with Daniel Robbins lately about the possibility of a common tree with Funtoo, I’m not sure he wants to do it the same way I do, which is unfortunate.

drobbins recent tipmade me think, that maybe I should point out that his solution to the problem is an annoying work around. I had this problem for a while, it was caused by my having autocrlf = input in my .gitconfig settings. Several people have told me that they have this problem without changing their crlf settings for git. After a while I decided that Funtoo/Gentoo’s git handling patches were incomplete at best and unfriendly at worst.

I had an interesting conversation with thewtex on #funtoo yesterday. My conclusion is, this divergence of tree’s is stupid. We should be working on a common base, at least common enough that users could relatively easily merge our tree’s. My tree is currently ahead of yours in content by 3 sunrise merges, 1 mpd, and the 2 merges of the python overlay. Your users can’t easily get these updates.Due to the fact that we have irreconcilable views on what patches we allow, the fork must remain.

So, I won’t be the Tree Maintainer for Funtoo anymore. In light of the new situation I’m forking Funtoo. I’m not going into details why I’m not the tree maintainer anymore on this blog, except to point out how Regen2 will differ.I’ll be continuing to maintain a tree with all the overlays I had added and more to come. you can get a copy of my version of portage at git://github.

I’ve decided I’m going to start posting a sort of weekly newsletter (I’m not committing to weekly though) merely to document anything I feel important that happened, or is about to, but isn’t quite important enough for it’s own post.RA(ra– on #funtoo) or r_a@lavabit.comsubmitted quite a few patches this week including 1 that fixes many of my major borkage on non-latin1 changelog breaks. He’s become a regular contributor and I’d like to thank him.

I’m adding the MPD overlay courtesy of Rullzer who’s kind enough to merge and maintain it in tree. Nothing big here, just some more up to date ebuilds, and more clients for MPD.–This workby Caleb Cushingis licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.

Soon, Dan Robbins will be merging my perl-experimental branch which contains the perl-experimental overlay. This overlay contains a handful of packages, the most important of which is perl-5.10.0 which has been out for about a year now and Gentoo still hasn’t put in portage. One nuisance of the perl-experimental overlay is they don’t use changelogs which means if you want to know what’s going on with a package from this you’ll have to check out git log as well as the changelog.