Archive for March, 2005

todo management

Monday, March 28th, 2005

michael, spy and others: I’ve found tomboy to rock for quickly letting me jot notes, keep tabs on what I’ve got next on my plate, etc. When a topic needs further detail, it’s a quick highlight, click “Link” and I’ve got a new note linked to from my main “gentoo work” note on which I can note more details about the given task.
To give you a little taste, here’s the two notes which recently have seen the most light of day.

Having note-taking be so quick, easy to search and bring up (tomboy runs as either a gnome panel applet, or as a notification area icon) lets me stop worrying about what tool i’m using to keep notes, and just focus on the content of the notes themselves.

You can emerge the slightly older tomboy-0.2.2 on stable x86 right now, I’m going to be marking tomboy-0.3.1 stable soon, pending resolution of one or two more bugs.

rant, my recent disposition, etc

Friday, March 25th, 2005

In one of the NY Times crossword puzzles last week, the clue for one of the answers was “Blog post, often”. The answer was, of course, “rant”. (For those that don’t know, i’m addicted to the NYT crossword puzzle, and have collected every puzzle i’ve done for about the last 3 1/2 years now.) Anyway, prepare yourselves for one of those “oftens”.
What spurned this on was lots of things, but today it kinda summed it up when someone in #gentoo-dotnet on freenode said:

<anonymous -guy-i-know>: don’t take this the wrong way, you’ve been kinda touchy recently, everything ok?

You know what? I have been. And i don’t like it. Beyond the usual RL (Real Life for those acronym impared out there) stuff, which has been bizarre and stressful, Gentoo stuff has been irking me and frustrating me in odd and annoying ways. Here’s a list of some of the things that have been bothering me recently. Having a b*tchfest is by no means something i like doing, and that’s not really the point of this post (although it’ll certainly act as one). What I’m more looking for is people’s opinions on maybe *why* some of these things are the way they are, and what can be done to avoid them.

  1. Being embarassed about Gentoo while participating in other public forums - It’s really sad, but I find myself not wanting to associate myself with Gentoo when talking in various IRC channels, on mailinglists, whatever. That sucks. I’m really proud of what Gentoo accomplishes, and how hard everyone involved in the project works. I think this is directly related to point #2.
  2. Vocal minority of users tarnishing “Gentoo” as a concept? - This point may make some people pretty angry, might not, i’m not sure. I think the first issue is directly related to a vocal minority of our users, whom most recently have been coined “ricer users”, whom seem to be willing to try the latest package.mask, BMG, love-sources, etc packages/kernels, without any concept of consequences or desire to actually know what they are doing or fix things themselves. Gentoo has always been “tinkerers distro”, but in my mind that concept only works when the people doing the tinkering actually have at least a basic knowledge of what they’re bloody tinkering with. I had someone in #mono complaining that they were having all these bugs recently with gentoo, and were fed up and going over to using ubuntu. Of course, the next comment they made was the fact that gnome-2.10 wasn’t compiling for them, but that it worked fine on ubuntu. If you’re gonna be using a package.masked and ~arch package, you’d better d*mn well have on your hard hat, and be ready to actually research and fix any problems you run into. Not to get too off-topic or rambling, but how do we keep users like this from “ruining Gentoo” in the eyes of everyone else? Perhaps Gentoo makes it *too* easy for people to try out things they shouldn’t be? Maybe we should remove all our docs about using package.unmask, package.keywords, and PORTDIR_OVERLAY, strike all posts about this from the forums, and kill on site anyone uttering the word “love-sources”? (I’m kidding, but sometimes I get so frustrated that it sounds like a good idea).
  3. In-fighting among devs - This one probably is one of those innevitabilities in life, but it still really gets to me. Having what i’d consider a pretty diverse interest in all-things-Gentoo, I end up getting involved in stuff all over the board in Gentoo. One of the things that consistently irks me is the bickering and downright hate displayed between some devs. Maybe i’m just too much of a hippy child or something, but I get really frustrated and upset when people start throwing insults, threats, accusations, etc on the mailinglists and IRC channels, etc. “Can’t we all just get along?”

Anyway, that concludes this edition of “Latexer complaining out load to lots of people who don’t care”. I’m gonna go get mono-1.1.5 into the tree now. Please feel free to leave comments here, although the viagra and texas hold ‘em spam might obliterate your feedback.

new monodevelop, mono (almost), invincibility

Tuesday, March 22nd, 2005

Well, there’s a new monodevelop and almost a new mono out. Looks like the new MD may just well be enough to force me to get gtk-sharp-1.9.x (the gtk-sharp-2.0 preview releases) into portage. That’ll mean new muine lovin’ for gentoo-ers too.

In preparation of that, I’ve fixed the deps in every but one package to handle the new SLOTing of gtk-sharp stuff (so people don’t have “gtk-sharp” installed but have tomboy fail to find it due to only 1.9.x being installed, etc) along with the help of a few others on bug #86328.

In other news, I went snowboarding for two days this past weekend with Stacey, and managed to completely f*ck up my back the second day. Was one of our last runs, and I was being lazy; I managed to catch a heel edge while making a lazy toe edge turn, and wiped right only my upper tail bone. not a pleasant feeling. Hurrah for ice.

mono, gtk-sharp, friends stable on x86

Monday, March 14th, 2005

Beware the stable mono-1.0.x!!!! MWA HA HA!

Waiting on a new monodevelop-0.6 that works better on mono-1.1.4, then hopefully we’ll see mono-1.1.4 out of package.mask (amd64 users will benefit most from this).

Now that we have a stable mono-1.0.x, all those packages with optional .NET bindings (dbus, gettext, libbtctl, etc) no longer have to hack around things when trying to mark a package stable. Hurray for that.

Haven’t marked muine or monodevelop stable yet, I’ll probably do those either later tonight or tomorrow.

Fear the dev-dotnet/mono -> dev-lang/mono move!

Thursday, March 10th, 2005

So, I’ve just finished moving dev-dotnet/mono to dev-lang/mono. Included making commits to fix deps on ~25 packages, as well as changes in use.local.desc, etc, etc, etc. Now *that’s* what I call fun. I’ve triple checked the tree to make sure no more references to dev-dotnet/mono are hiding, but all you people with custom ebuilds, etc will have to update them.

I’ve got a new tarball of my overlays up here for people, and the seperate stuff is up in the usual place.

This was my last major hurdle before I’m ready for a mono-1.0.x stable, so once this settles, look out for mono lovin’.

EDIT: I’d forgotten one thing in my overlay, so i’ve updated the link to the tarball to todays, and fixed it in my broken out stuff in my dev space.

Hello Planet!

Thursday, March 10th, 2005

Hello Planet Gentoo!

To make this something more than spam: I’ve been pretty busy lately, work + GF + gentoo stuff, the usual. Pending one or two small niglets, i’m hoping to finally (i know, i’ve been saying this for a while) get a mono-1.0.x marked stable!!! more to come soon.