Ralph,<br><br><div><span class="gmail_quote">On 21/07/2008, <b class="gmail_sendername">Ralph Angenendt</b> <<a href="mailto:ra%2Bcentos@br-online.de">ra+centos@br-online.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alan Bartlett wrote:<br> > The second reference you have quoted actually details how to obtain the<br> > Kernel Sources and set up the build tree in a consistent fashion for<br> > subsequent usage (covered in two other articles).<br>
<br>And you cannot see the problem there? </blockquote><div><br>The only problem *here* is that you misunderstand what I wrote (which you quote, above).<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So it is already there - in three<br> different articles</blockquote><div><br>Sorry Ralph, you are wrong. I said the above to point out that the article Fillipe quoted (erroneously) in the following:<br><br>"<span class="q">to set up your<br>
> environment to build RPMs and how to rebuild RPMs. This content today<br>
> exists here:<br>
> <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://wiki.centos.org/HowTos/I_need_the_Kernel_Source#head-a8dae925eec15786df9f6f8c918eff16bf67be0d" target="_blank">http://wiki.centos.org/HowTos/I_need_the_Kernel_Source#head-a8dae925eec15786df9f6f8c918eff16bf67be0d</a></span>"<br>
<br>is referred to by two other articles in that How To sub-section.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> - and has to be changed *everywhere* if some small<br>
aspect of rpm building changes.</blockquote><div><br>Once what I have written is understood, your preceding comment is seen to be quite incorrect. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Having to change that in *one* place and let all other places link to<br> that is a much cleaner approach.</blockquote><div><br>That is *exactly* what we do . . . and I cannot think of anything cleaner than:<br><br>$ mkdir -p ~/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}<br>
$ echo "%_topdir %(echo $HOME)rpmbuild" > ~/.rpmmacros <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> >> Basically I think that pointers to the outside are not that good<br>
>> because they not necessarily contain CentOS specific information.<br> ><br> > The main link that Akemi and I currently have in Kernel Sources and Custom<br> > Kernel is to the (maintained) CentOS specific Owl River page (<br>
> <a href="http://www.owlriver.com/tips/non-root/">http://www.owlriver.com/tips/non-root/</a>). The other link, in the Custom<br> > Kernel article, (<a href="http://howtoforge.com/kernel_compilation_centos/">http://howtoforge.com/kernel_compilation_centos/</a>) is<br>
> mentioned to strongly dissuade its use.<br> <br>Still: People tend to go to the CentOS wiki for finding information (or<br> they are pointed to it). And I'd like to have information like that<br> available *in* the wiki where more than one person can change it should<br>
the need arise.</blockquote><div><br>Perhaps there is an error on my part by using the expression "main link" when I should have said "main references" - for that is what they are, references. These references can be removed *without* any loss of information, etc. For this error, I apologise. <br>
</div><br><div>The other problem is that you seem to have ignored the rest of my message dated 19 July - that neither attacked any person *or* idea - or the second one of the same date. The English language is very precise when it is used correctly. Problems do arise when it is misused or misunderstood.<br>
<br>Please review your reaction and response.<br><br>Alan.<br> </div></div><br>