I find the analogy also holds like this:
Unlike the do-it-yourself hot rods of the fifties, one of the implications of calling a car a "ricer" is that it's composed of a bunch of bolt-on performance enhancing kits and accessories. You get the feel that you've built a hot rod, and all the tweaking and fiddling needed to keep the bits from falling off or out of sync makes you feel like quite the mechanic, but you're not an engineer or a machinist.
In like manner, all those meaningless messages scrolling off your screen too fast to read when you do an emerge world make you feel like some 'leet coder, even if you wouldn't know what they meant if you _could_ read them. Yeah, you can get under the hood and mess with the USE flags and the package masks - but you're really just pressing the same button as someone using aptitude.
Yeah, you learn a lot about how to fix the gentoo package sysetem, but it's gentoo specific knowledge, seldom applicable to any other linux distro.
Source packages, and instructions on how to tune and rebuild them, are available for all of the binary distros I know of.
On Fri, Jan 05, 2007 at 02:24:00PM -0600, Luke -Jr wrote:
On Friday 05 January 2007 13:44, Jonathan Hutchins wrote:
Source packages, and instructions on how to tune and rebuild them, are available for all of the binary distros I know of.
But it's bad practise to install from source on a binary OS.
That is why I build rpm's first and install those.
-- Hal
On 1/5/07, Luke -Jr luke@dashjr.org wrote:
On Friday 05 January 2007 13:44, Jonathan Hutchins wrote:
Source packages, and instructions on how to tune and rebuild them, are available for all of the binary distros I know of.
But it's bad practise to install from source on a binary OS.
Why bad practice? Isn't that what ports for on *BSDs is for? Since the *BSDs don't have the power nor the will to compile all those ports into packages specially on ports that a small select group use.
On Friday 05 January 2007 23:44, djgoku wrote:
On 1/5/07, Luke -Jr luke@dashjr.org wrote:
On Friday 05 January 2007 13:44, Jonathan Hutchins wrote:
Source packages, and instructions on how to tune and rebuild them, are available for all of the binary distros I know of.
But it's bad practise to install from source on a binary OS.
Why bad practice? Isn't that what ports for on *BSDs is for? Since the *BSDs don't have the power nor the will to compile all those ports into packages specially on ports that a small select group use.
*BSD aren't binary OS, IIRC
On Friday 05 January 2007 13:44, Jonathan Hutchins wrote:
Source packages, and instructions on how to tune and rebuild them, are available for all of the binary distros I know of.
On Friday 05 January 2007 14:24, Luke -Jr wrote:
But it's bad practise to install from source on a binary OS.
Right, so you build the binary package yourself (similar to compiling) and install _that_, and stay within the benefits of the package management system.
With the source packages from a binary distro, they have all the files necessary to build as distributed, and you are free to adjust flags and features.