Dirk, Nothing. I got everything working including a full set of release binaries (for Linux). After going through some documents, I figured out the issue that I was having.
1. I moved to python-lxml2 + python-lxst1 (names may not be exact). 2. I figured out I was not getting document content updates as I expected because I wasn't running the #bin scripts. I suppose we could make a PR for evaluating why python-lxml support does not seem to like the chunked html output. V/R, William On Mon, Aug 22, 2016 at 5:50 PM, Dirk Bächle <tshor...@gmx.de> wrote: > Hi William, > > On 21.08.2016 17:53, William Blevins wrote: > >> >> [...] >> >> I would argue that "the normal user" never runs the document building >> scripts, so I don't see how that applies. >> > > it applies because the building scripts, and the Doc toolchain, around it > is especially designed and setup such that "the normal user" can run them > without having to install too many additional dependencies. He doesn't get > an updated example text or a refreshed Builder description, but if he > simply edited or changed a paragraph in one of the chapters he certainly > shouldn't mind. > > >> As I said, I haven't been in this community long, so I don't know the >> history of SCons (not really). How and why were some decisions >> made? As I work on the code, those questions aren't irrelevant. Text has >> this way of removing body language. I hope I don't sound >> combative because that's not my intention. I just like being frank, and I >> like questions. I have a weird mix of software development >> and tester experience, so questions just come with the territory. I also >> tend to use emails like others use instant messaging. I >> think it comes with the age demographic. This tends to annoy people. >> Sorry :) >> >> > That's okay. > > But what is the actual remaining problem that you would like to tackle? > The docs rebuild when one of the chapter *.xml files change, which is what > I'd call "correct behaviour". > > Regards, > > > Dirk > > _______________________________________________ > Scons-dev mailing list > Scons-dev@scons.org > https://pairlist2.pair.net/mailman/listinfo/scons-dev >
_______________________________________________ Scons-dev mailing list Scons-dev@scons.org https://pairlist2.pair.net/mailman/listinfo/scons-dev