I managed to model and render something on this
computer finally.

FIRST the JARGON way I write...

Through the process I have discovered
that this current build with the graphics patch isn't
as stable as I hoped. I'm wondering if that is because I pulled
source from trunk. I could try again with source from a
release branch given the fact that I want something as stable
as possible minus the graphics slow down issue.

So, I'm holding off on releasing my binary for a bit.
Besides, I wanted to adequately warn future binary users
about the issues involved.

Perhaps that sounded more like....

Through the process I have discovered
that this BLAH BLAH BLAH with the graphics BLAH isn't
as BLAH as I hoped. I'm wondering if that is because I pulled
BLAH from BLAH . I could try again with BLAH from a
BLAH BLAH given the fact that I want something as BLAH
as possible minus the BLAH BLAH BLAH issue.

So, I'm holding off on BLAH my BLAH for a bit.
Besides, I wanted to adequately warn future BLAH BLAH's
about the issues involved with using the word BLAH.

Does anyone else think it's strange that
'Jargon' was a jargon word until you learned it?

NOW the LAYMEN way I could write...

If the above doesn't make much sense to you, what with the
trunk and the branching and all than don't worry.
I'll explain more thoroughly.

You see blender development,
(as a lot of open source software BLAH goes)
splits the main source code of the program into
directories aka folders upon different releases.

They are known as branches.

Now the source code, the main code that sprouts off these
branches is known as trunk. This is simply a way to refer
to the main folder full of all the code that the developers
can work from. It represents the most up to date version of
blender. (sort of)

The binary or runnable double clickable application I
compiled (made) was build from trunk.

The location of the code sits in a thing called a repository.
That's where all the source code hangs out before a developer
pulls it from it's slumber and bakes it into a fully
running program.

The software we use to manage all these folders or (branches) is
called SVN. SVN is itself a program that you run from the command line.
The command line is a place where rather than clicking on an icon and
running a program we can simply type it's name.

Hence by typing

svn info

I was able to get all this data about the blender trunk
when I compiled.

URL: https://svn.blender.org/svnroot/bf-blender/trunk/blender
Repository Root: https://svn.blender.org/svnroot/bf-blender
Repository UUID: 954f8c5b-7b00-dc11-b283-0030488c597c
Revision: 17916
Node Kind: directory
Schedule: normal
Last Changed Author: theeth
Last Changed Rev: 17914
Last Changed Date: 2008-12-17 14:52:13 -0800 (Wed, 17 Dec 2008)

You can see that the URL is pointing to something with
the word trunk in it. See it's a folder. The information also
tells me Revision Number. As developers commit code
to the repository the changes are numbered. Hence I compiled
the 17916th revision of blender's source code. And theeth
was the last developer to commit a change.

As to how stable it was before I patched it? I have no idea.

Regardless, I was trying to explain what branches were.

If your're using FireFox... and I hope you would since my site
is broken in IE6.
Try visiting
https://svn.blender.org/svnroot/bf-blender/

You'll notice the link branches/ there right away.
When I said the trunk is where development goes on sort of
I was holding back in explaining that all these other folders
contain source code for blender with different focuses and emphasis.
This is to prevent errors in one branch from interfering with another.
That way developers can hack away at the code with
out worrying about someone else's changes wreaking their
work... until later of course when they merge back into
trunk. (But that's a whole'nother topic)

You might notice a branch called blender2.5/
That's where the bulk of the work for 2.5 is going on right now
and it is what I tried to compile last night as well.
Not much luck with it yet bit if there was ever going to be
a permanent fix for the graphics issues in GMX this is where
they would be hanging out.

At this point please consider re-reading the first JARGON
paragraph and patting your self on the back. It should make
much more sense to you. Consider your learning curve to be
beautiful.

JARGON again...

Regardless, I was thinking of compiling and patching to
the blender-2.48-release/ sitting in the tags folder for
stability. Since the whole point of this build is to be stable.
So I decided to see if i could do that before I tried
to release a binary to the community.

Also, I hadn't done a movie for it yet.

This took all day.

Happy Holidays.
except for you frontbuffer GL bug. I hate you.