On Sunday 02 December 2007 08:12:05 am Carlos E. R. wrote:
> The Sunday 2007-12-02 at 06:52 -0600, Rajko M. wrote:
> >>> You should better follow the instructions in
> >>> "/usr/src/linux/README.SUSE", which actually is
> >>> "/usr/share/doc/packages/kernel-source/README.SUSE". There is no
> >>> reference to "make mrproper" in there: that target can break things
> >>> sometimes, IMHO.
> >>
> >> Such as...?
> >
> > Broken kernel source tree ;-)
> >
> > Carlos:
> > make mrproper is valid target if you want to remove all traces of
> > previous compilation(s) and start from scratch, if it breaks something it
> > is better to know at 

that == compilation 

> > stage than later when kernel doesn't work 
> > properly.
>
> It is a valid target when you get the sources elsewhere, add bits and
> ends, etc.
>
> It is not needed if you just install the source rpm from suse, which comes
> already cleaned. It can delete customizations, too: the only time I used
> it deleted my own config files and notes, and some of suse's files. I had
> to reinstall the sources. It deletes *anything* it thinks doesn't belong
> on the kernel.

That is the purpose of 'make mrpoper'. If you need config files than you have 
to move them in safe place before, let 'Mr. Proper' [1] do the job for the 
rest of the tree and than move them back. 

> If you need to clean a previous compilation, use "make clean". That's more
> than enough.

On this one I would need advice of some kernel developer. 

> I have been making my own kernels for years and I never use mrproper. SuSE
> does not recomend it in their own instructions. It's not even mentioned.

Don't say that I don't read your posts carefully ;-)
If it is not mentioned than we don't know what they think about it. 

Though, they are developers, so they would know how to remove it if it can 
damage openSUSE specific settings, or adjust not to delete openSUSE patches 
that are not yet included in upstream kernel. 

-- 
Regards,
Rajko
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to