?

Log in

No account? Create an account
Oh crap - The tissue of the Tears of Zorro [entries|archive|friends|userinfo]
tearsofzorro

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

Oh crap [Dec. 18th, 2006|11:15 pm]
tearsofzorro
[Tags|, , ]

I think I may just end up breaking my gentoo desktop for the next while (until I fix it)

Updating things like gtk must really only be done when one is NOT running things that rely on it... like gnome.

hmm... this'll be interesting.
linkReply

Comments:
[User Picture]From: ebel
2006-12-18 11:57 pm (UTC)
Ha ricers.

Now if you didn't have to compile *everything* you could just reinstall gnome in a few minutes. :P
(Reply) (Thread)
[User Picture]From: tearsofzorro
2006-12-19 09:27 am (UTC)
True, but by the time I've broken/re-installed/recompiled everything, I'll know a LOT more about my system than others ;)
(Reply) (Parent) (Thread)
[User Picture]From: ebel
2006-12-19 09:33 am (UTC)
Hmm maybe about somethings.

I think developing for a system teaches you a lot more than passivly compiling everything. After all when you emerge gnome, it figures out the dependencies. If you start hacking on gnome, you'll probably learn a lot more about gnome.

Likewise write bash shell scripts teaches you more about bash than compiling bash does.

YMMV etc etc
(Reply) (Parent) (Thread)
[User Picture]From: tearsofzorro
2006-12-19 11:40 am (UTC)
Very true. But I didn't quite mean it in that sense.

Gentoo gives me an opportunity that has been missing in my life for a while - the opportunity to Break Stuff (tm). This generally tends to be quite a learning experience. Let's say I accidentally upgrade stuff, and suddenly all the graphics in gnome decides it's really not going to work now... I now know what happens when I break things.

Naturally, just compiling something wouldn't change anything... like I could just as easily be compiling something that prints "poop\n" 5 million and one times.

So it's not the fact that I've recompiled things lots has taught me, but the fact that I've HAD to recompile them is the lesson. The extra time taken to actually upgrade is the pain to the lesson to make sure I remember it.

I should really write a book, "The masochists guide to Linux"

Step 1. Get a barbed garter and place it around your left thigh. The pain brings purity of thought.
Step 2. Now we learn about emerge!

;)
(Reply) (Parent) (Thread)
[User Picture]From: ebel
2006-12-19 12:18 pm (UTC)
True, but what does fixing something on gentoo involve? Can you just remove & remerge? Or just tell it to emerge update (and hence have it finish all updates)? Cause that wouldn't be very educational....
(Reply) (Parent) (Thread)
[User Picture]From: tearsofzorro
2006-12-19 01:57 pm (UTC)
Yes. You can remove and remerge... if you're at that stage, you already know the library at fault.

Now, I get that you can learn a metric shitload more if you actually start diving into the code and the like... but the process was transparent enough so that I could:
a/ See that it was GTK+ what done it.
ii/ See what it was GTK+ what done.

(actually, I think I was writing my original post just as I realised I was going to break some things quite spectacularly).

And yes, I can tell emerge just to update my world file... but right at the moment, that'll involve well over a gig of downloads and a weekend of recompiling. And it wouldn't be that educational. Right at the moment, my current education is telling emerge that "No. I don't want to compile all those X.org drivers, because I don't have the bloody cards for them!" then I could probably turn my hand to gnome.

It's one of the reasons I like to do this stuff by hand...I get to see what I end up breaking.
(Reply) (Parent) (Thread)