On Wednesday 14 November 2001 02:55 pm, Epicurus wrote:
> > The main problems with usin vanilla source are you need to be
> > savvy enough to read the Makefile, figure out ahead of time where
> > the software will be installed and what it's fixin to do. Then
> > either edit/patch that file/source to fix it to be 'your distro'
> > specific, or use the appropriate switches.
>
> Well now, what exactly are you speaking about in terms of fixing it
> to be 'your distro' specific?
"exactly" would take a book I probly couldn't begin to write.
Would you be content with 'where the libs, and binaries are installed
to' ? Didn't think so ;) To elaborate just a little more, there's
compiler issues, the LSB (to which Mandrake is very compliant),
dependencies, libraries, devices, ad infinitum other issues.
> So what I'm really wondering is if I can use the old-fashioned
> methods of rebuilding the kernel, updating the c libraries, and
> installing some programs, while still using rpms from time to time
> as well.
No, not really. There's issues of leaving your rpm database
(which others in this thread brought up, I neglected) totally
confused. AND kernels bring up another issue, which I sort'a kind'a
alluded to before. Many, specially those recent to Linux, seem
to get the idea that vanilla source from kernel.org is pristine
latest and greatest kernel source. Many oldtimers still cling to this
notion.
Vanilla kernel source from kernel.org should be considered beta,
if not alpha quality. Even after the next -pre, -ac or -linus is
released, the last one isn't 'fixed'. It's a continual state of
development. Mandrake (or other distro) kernel rpms OTOH, at least
have had the attention of many Mandrake ((or other distro) developers
and testers. They include Mandrake specific patches, and exclude some
that might cause conflicts.
YMMV, but I'd never use anything but a Mandrake kernel rpm to
install a kernel on a Mandrake system. It only stands to reason that
Mandrake tested and patched kernel source stand's a better, much
better chance of working without problems on a Mandrake system. For
example, the 2.4.8 kernel ML 8.1 shipped with had some 2.4.9 'fixes'
back ported to it by the Mandrake developers (lurk on cooker ML ;)
BUT, to get back to rpms vs. source. There's been some definitely
good and necessary reasons most major distros moved to packages long
ago, rather than willy-nilly upgrading from vanilla source. Many
reasons have already been brought up in this thread by myself and
others. Plus from the distro developers's POV, how could they
possibly begin to try'n support their distro with the endless
permutations of thousands of users grabbin all kinds of vanilla
source, plus tarballs with closed source included ? It's already bad
enough that their users are tryin to run on endless permutations of
hardware (and install'n some third party closed source drivers to do
it ;)
--
������Tom Brinkman � � � � � � � � Galveston Bay, USA
chmod +x --with -daisy_cutters /bin/Laden.al-Qaeda.Taliban
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
