On 01/25/2013 01:09 PM, Randy McMurchy wrote: > On 1/24/2013 7:44 PM, Armin K. wrote: >> >> I'd like to know how do you know when to use option or parameter. On >> this one you are changing parameter to option, while below you are >> changing option to parameter. > > The Editor's Guide lays it out precisely. Parameter is used for switches that > are actually used in the instructions. Option is used for things that are > optional and are not actually in the instructions, only there to let readers > know something. It is easy when you think about it. > > >> Just curious. I was always using template/template.xml for that case. > > I made that template years ago. If I recall correctly, there was an example > parameter and an example option. They were there so there would be one of each > as a reminder to other editors. > >
Yeah, that makes sense now. Could you correct current template? I think that Andy modified it. >> >> Why did you comment out Cups? It is used for CUPS bluetooth backend. > > No, it is not. Cups is not used by the package. It does create the backend > but does not link anything from cups to it. In fact if you see the description > of the option in Command Explanations you will see that I mention that CUPS > need not be installed. > > >> Now that you pointed it out, I've checked it again, and it is correct. >> Also, same applies for --enable-alsa. You could just remove all of the >> code instead of commenting it out. Keeps files cleaner. > > I prefer to comment out stuff the first time around. That way if there is a > screw up, it is much easier to put it back. It can always be deleted later. > Having commented code in the .xml files is still "clean". > > Sure, that's okay with me. Now I noticed, as I said in the other mail, that --enable-cups is required to enable CUPS backend. And it does not use the CUPS at build time, but backend is practicaly useless without CUPS at runtime ... >> >> This is strange. All tests passed on my side. You need to run them from >> a GUI though. > > I did. Here is what I got: > http://www.linuxfromscratch.org/~krejzi/check.txt This is mine. I don't know why are you getting that. >> I've always wanted to ask for this one. >> >> Can't we just stop explaining --whateverdir=/path/to/whatever switches? >> I mean, it should be obvious that it is setting installation paths for, >> lets say, docs, executable, whatever. > > I agree But if they are already in the book, what is the harm in keeping them? > There is no harm, but I guess we can stop doing that in the future (for new packages, etc), if you agree. > Hopefully, I responded to all your comments. But because you did not trim any > of the original post, it makes it really hard to follow. I trimmed it up so > that we can read it better. > Thanks for your time. -- http://linuxfromscratch.org/mailman/listinfo/blfs-book FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
