Husse wrote:This is what our homepage states about source
If you want to access their source code you can use the apt-get source command. If you can't find what you're looking for please write to root AT linuxmint DOT com and we'll provide the source to you.
Thanx, Ill try get the source and maybe make my own Debian Mint, Arch forums is one of the rudest places Ive been to yet, they act like you should know everything about Arch right out the gate, and treat you like you're an idiot if you don't, so I'm gonna try something else, and then try to Mintify that.
The same command works in pure Debian
If you're looking to compile the Mint Tools into Etch, IIRC, you'll also have to compile a newer GTK, libc, glib, etc... and whatever *those* .debs will in turn need, dependency-wise. So, it might be easier to grab a daily snapshot of Lenny, or aptitude dist-upgrade to Lenny from an Etch install first
Also, a good package to install, after installing Lenny, is the apt-listbug package - it'll give you a nice warning before doing anything you might regret
But, in my experience, there's very little (if any at all) performance difference between binary and compiled Debian packages and installations. Even in Gentoo, with all of your useflags set correctly, etc... the performance is usually so minimal it's all about bragging rights
It's undeniably fun, and enabling everything and the kitchen sink, setting your CPU flags just right (-nocona here, for instance), and then recompiling your entire system is pretty cool, but doesn't net you a whole lot in real-life use
And in Debian, compiling is rather different. I'm not trying to bash - man, it's geeky fun if you have the time - but there's *very* little difference