On Wed, May 4, 2016 at 10:44 PM, Ken Moffat <[email protected]> wrote:
> On Wed, May 04, 2016 at 04:17:32AM -0400, Tim Abracadabra wrote: > > On Tue, May 3, 2016 at 12:37 PM, Ken Moffat <[email protected]> > wrote: > > > > > On Tue, May 03, 2016 at 03:28:40AM -0400, Tim Abracadabra wrote: > > > > > > > > > > I'd be happy to help contribute in making the change. > > > > > > > > -- Tim > > > > > > Tim, I'll be committing that wording soon. We can discuss changes > > > to revise it if you (or anybody else) think it can be better worded. > > > > > > ĸen > > > > > > ken, The wording in Changeset 11051 nails it! > > I did however have one observation. > > The relationship between the initial config and the one for XSParagraph > may > > not be obvious to some users. > > Maybe insert: called or internally called to clarify their relationship. > > Otherwise someone might wonder if XSParagraph is different step in the > book > > or .. > > > > Example “ .. this is an unrecognized option, but the internally called > > configure script for XSParagraph recognizes .. > > > > -- Tim > > Thanks for the comment (I've been away from my mail for a few hours, > trying to update my BLFS scripts to last week so that I can look at > texlive 2016 - nothing special about last week, except that was when > I decided I needed to do this). > > I think that we need to accustom people to the idea that a package > might have multiple configure scripts - the main one which causes > problems in LFS-support is binutils. This package comes a long way > after that, but I am not convinced that adding "internally called" > will be generally useful. > > ĸen > Thanks Ken for your support, Indeed you are driven and busy ! I just want to say, I am hugely impressed with the quality of the LFS book, It's the best! Typically, If you follow it, it just works. (*There may be host system considerations). The text not only instructs but teaches with encouragement. I also realy love the BLFS documentation. I discovered it while I was in chapter 5 and it really gave some great tips and details that really helped. Thanks to all who work so hard to make it so. Back to the topic: In retrospect, I agree with you that adding "internally called" might be a bit on the side of .. handholding. However - I still stand by my opinion that there should be something in the wording that indicates a direct relationship between the "top-level" configure and the "called" configure in XSParagraph. In my view, just adding the word *called* in the place I mentioned will help "accustom people to the idea that a package might have multiple configure scripts" (<quote) by clarifying their relationship. Some users might not at first realize the importance of the phrase "top-level script".Then they would read further and say wow, configure may *call* another script and then tie both references together and ... learn ! That's my $0.02. But like I said previously, You Nailed It and I am thankful for your inclusion. -- Tim
-- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
