Re: [Scons-dev] User-guide generation

[William Blevins]

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  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

Re: [Scons-dev] User-guide generation

[Dirk Bächle]

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

Re: [Scons-dev] User-guide generation

[Dirk Bächle]

Hi William,

On 20.08.2016 00:22, William Blevins wrote:

Dirk,

...

Right and I understand that there is documentation, and I use it when I have an 
issue. The problem that I have is that I have worked
with the docs more than most (outside the maintainer team), and I always seem 
to forget about the #bin scripts. In my opinion, a
good process is intuitive and doesn't have lots of manual steps. I think it 
would be a good idea to have the SConstruct in #doc/user
to Execute the #bin scripts in order. I don't think it would cause any issues, 
but would make generating the docs a 1-step process.
Is there a reason not to do something like this?



the main reason for this is, I guess, that the generation of examples needs a lot of time. And there are people out there that don't 
like seeing this step being repeated over and over again, whenever they make minor changes to the documents and want to receive 
"immediate" visual feedback.





. The normal user, only doing simple edits and changing text passages, 
shouldn't have to care about regenerating the output of
the examples. He can run the validate script, and then compile the user 
guide for example, such that he gets an idea how the
final PDF/HTML output might look like.
Everything beyond this point is in the scope of the actual release team. 
This separation is there to make it as easy as possible
for new contributors to add or amend documentation. The required validation 
ensures that the checked in and merged doc changes
by a user can be compiled into a correct document later on by a release 
manager, sort of justifying the usage of Docbook all
together.


I don't see the harm in a regular developer getting a generated document that 
reflects the changes made. If I make changes to
documents and regenerating the user guide doesn't show my changes, then it gets 
very puzzling.



I was talking about "the normal user" (read: occasional contributor), why do you now switch to what the "regular developer" can 
expect or not?

I understand that in your case both of these roles seem to coincide, but this 
is not true for the majority of people out there.



I hope this makes things a little clearer.

Finally, the UserGuide should also get recompiled when you change one of 
the chapter *.xml files. If this doesn't happen that
would clearly qualify as a bug...


It rebuilds. We may want to change the wiki documentation though, because 
python-lxml does not appear to work correctly with the
chunked guides index.html. I moved to python-libxml2 and python-libxslt1 and 
that seemed to make things happier.


Another option might be to find out *why* the python-lxml binding doesn't seem 
to work, and then make it doing so. ;)

Best regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User-guide generation

[Dirk Bächle]

William,

On 19.08.2016 13:14, William Blevins wrote:

Dirk,

Apparently, the user guide data doesn't regenerate unless you call:

python bin/docs-update-generated.py
python bin/docs-validate.py
python bin/docs-create-example-outputs.py

I guess it just doesn't make a lot of sense to me why these are manual steps 
rather than being commands that run as part of the
#doc/user build step.



please have another look at

  https://bitbucket.org/scons/scons/wiki/DeveloperGuide/Documentation

. The normal user, only doing simple edits and changing text passages, shouldn't have to care about regenerating the output of the 
examples. He can run the validate script, and then compile the user guide for example, such that he gets an idea how the final 
PDF/HTML output might look like.
Everything beyond this point is in the scope of the actual release team. This separation is there to make it as easy as possible for 
new contributors to add or amend documentation. The required validation ensures that the checked in and merged doc changes by a user 
can be compiled into a correct document later on by a release manager, sort of justifying the usage of Docbook all together.


I hope this makes things a little clearer.

Finally, the UserGuide should also get recompiled when you change one of the chapter *.xml files. If this doesn't happen that would 
clearly qualify as a bug...


Best regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User-guide generation

[William Blevins]

Dirk,

Apparently, the user guide data doesn't regenerate unless you call:

>python bin/docs-update-generated.py
>python bin/docs-validate.py
>python bin/docs-create-example-outputs.py
>
> I guess it just doesn't make a lot of sense to me why these are manual
steps rather than being commands that run as part of the #doc/user build
step.

V/R,
William

On Fri, Aug 19, 2016 at 8:09 AM, Dirk Bächle  wrote:

> Hi William,
>
> I hope you don't mind since we're among developers here, but I think it's
> fair to apply the same rules to everyone.


Sure. I'm don't even know what you would have done otherwise. Laugh? Also
acceptable :)


> So I'm treating this the same as on the user list.
> Please tell us which commands exactly you have run, and which parts of the
> documentation you follow as reference. The "doc/user/SConstruct" should
> work fine and is supposed to allow you to build the corresponding
> PDFs/HTMLs standalone, during editing for example.
> So simply removing it is not an option at the moment.
>
> Best regards,
>
> Dirk
>
>
> On 19.08.2016 06:32, William Blevins wrote:
>
>> Team,
>>
>> While I was chasing my tail, I went ahead and followed the
>> SimplifiedReleaseProcedure
>> > iedReleaseProcedure>. Not sure how to verify I did it right. What's the
>> process for handing out alphas?
>>
>> I didn't make a branch or anything. This was just for my personal
>> reference.
>>
>> V/R,
>> William
>>
>> On Fri, Aug 19, 2016 at 4:54 AM, William Blevins > > wrote:
>>
>> Team,
>>
>> I think I chased my tail until I figured out I needed to run some
>> python scripts under #bin which do fairy magic...
>>
>> V/R,
>> William
>>
>> On Fri, Aug 19, 2016 at 4:12 AM, William Blevins <
>> wblevins...@gmail.com > wrote:
>>
>> Team,
>>
>> Is the doc/user/SConstruct legacy? If I build from #SConstruct
>> then I seem to get some not insane in the build directory. If
>> doc/user/SConstruct is no longer functional or maintained, I
>> would like to remove it to alleviate my confusion!
>>
>> V/R,
>> William
>>
>> On Fri, Aug 19, 2016 at 3:18 AM, William Blevins <
>> wblevins...@gmail.com > wrote:
>>
>> Team,
>>
>> I have a strange issue. The user-guide build does not throw
>> any errors but doc/user/index.html does not regenerate and
>> doc/user/scons-user/index.html is empty. All the addition
>> html files under doc/user/scons-user seem to generate correctly.
>>
>> Anyone else have this issue?
>>
>> V/R,
>> William
>>
>>
>>
>>
>>
>>
>> ___
>> 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
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User-guide generation

[Dirk Bächle]

Hi William,

I hope you don't mind since we're among developers here, but I think it's fair to apply the same rules to everyone. So I'm treating 
this the same as on the user list.
Please tell us which commands exactly you have run, and which parts of the documentation you follow as reference. The 
"doc/user/SConstruct" should work fine and is supposed to allow you to build the corresponding PDFs/HTMLs standalone, during editing 
for example.

So simply removing it is not an option at the moment.

Best regards,

Dirk


On 19.08.2016 06:32, William Blevins wrote:

Team,

While I was chasing my tail, I went ahead and followed the 
SimplifiedReleaseProcedure
.
 Not sure how to verify I did it right. What's the
process for handing out alphas?

I didn't make a branch or anything. This was just for my personal reference.

V/R,
William

On Fri, Aug 19, 2016 at 4:54 AM, William Blevins > wrote:

Team,

I think I chased my tail until I figured out I needed to run some python 
scripts under #bin which do fairy magic...

V/R,
William

On Fri, Aug 19, 2016 at 4:12 AM, William Blevins > wrote:

Team,

Is the doc/user/SConstruct legacy? If I build from #SConstruct then I 
seem to get some not insane in the build directory. If
doc/user/SConstruct is no longer functional or maintained, I would like 
to remove it to alleviate my confusion!

V/R,
William

On Fri, Aug 19, 2016 at 3:18 AM, William Blevins > wrote:

Team,

I have a strange issue. The user-guide build does not throw any 
errors but doc/user/index.html does not regenerate and
doc/user/scons-user/index.html is empty. All the addition html 
files under doc/user/scons-user seem to generate correctly.

Anyone else have this issue?

V/R,
William






___
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

Re: [Scons-dev] User-guide generation

[William Blevins]

Team,

While I was chasing my tail, I went ahead and followed the
SimplifiedReleaseProcedure
.
Not sure how to verify I did it right. What's the process for handing out
alphas?

I didn't make a branch or anything. This was just for my personal reference.

V/R,
William

On Fri, Aug 19, 2016 at 4:54 AM, William Blevins 
wrote:

> Team,
>
> I think I chased my tail until I figured out I needed to run some python
> scripts under #bin which do fairy magic...
>
> V/R,
> William
>
> On Fri, Aug 19, 2016 at 4:12 AM, William Blevins 
> wrote:
>
>> Team,
>>
>> Is the doc/user/SConstruct legacy? If I build from #SConstruct then I
>> seem to get some not insane in the build directory. If doc/user/SConstruct
>> is no longer functional or maintained, I would like to remove it to
>> alleviate my confusion!
>>
>> V/R,
>> William
>>
>> On Fri, Aug 19, 2016 at 3:18 AM, William Blevins 
>> wrote:
>>
>>> Team,
>>>
>>> I have a strange issue. The user-guide build does not throw any errors
>>> but doc/user/index.html does not regenerate and
>>> doc/user/scons-user/index.html is empty. All the addition html files under
>>> doc/user/scons-user seem to generate correctly.
>>>
>>> Anyone else have this issue?
>>>
>>> V/R,
>>> William
>>>
>>
>>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User-guide generation

[William Blevins]

Team,

I think I chased my tail until I figured out I needed to run some python
scripts under #bin which do fairy magic...

V/R,
William

On Fri, Aug 19, 2016 at 4:12 AM, William Blevins 
wrote:

> Team,
>
> Is the doc/user/SConstruct legacy? If I build from #SConstruct then I seem
> to get some not insane in the build directory. If doc/user/SConstruct is no
> longer functional or maintained, I would like to remove it to alleviate my
> confusion!
>
> V/R,
> William
>
> On Fri, Aug 19, 2016 at 3:18 AM, William Blevins 
> wrote:
>
>> Team,
>>
>> I have a strange issue. The user-guide build does not throw any errors
>> but doc/user/index.html does not regenerate and
>> doc/user/scons-user/index.html is empty. All the addition html files under
>> doc/user/scons-user seem to generate correctly.
>>
>> Anyone else have this issue?
>>
>> V/R,
>> William
>>
>
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User-guide generation

[William Blevins]

Team,

Is the doc/user/SConstruct legacy? If I build from #SConstruct then I seem
to get some not insane in the build directory. If doc/user/SConstruct is no
longer functional or maintained, I would like to remove it to alleviate my
confusion!

V/R,
William

On Fri, Aug 19, 2016 at 3:18 AM, William Blevins 
wrote:

> Team,
>
> I have a strange issue. The user-guide build does not throw any errors but
> doc/user/index.html does not regenerate and doc/user/scons-user/index.html
> is empty. All the addition html files under doc/user/scons-user seem to
> generate correctly.
>
> Anyone else have this issue?
>
> V/R,
> William
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide generation questions

[William Blevins]

That may be a valid problem though because when I run *scons* from #
*doc/user* the index.html generated from the build is completely empty.

V/R,
William


On Fri, Aug 29, 2014 at 6:44 PM, Dirk Bächle tshor...@gmx.de wrote:

  On 30.08.2014 00:12, William Blevins wrote:

 I am trying to make some misc updates to the User Guide, and I am having
 some issues. I thought it might be a problem with a document do I tried
 docs-validate and there were two errors:

  [...]


   81.11% (176/217) doc/user/scons_ex.xml
 ERROR: doc/user/scons_ex.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc, {http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4116
 81.57% (177/217) doc/user/sconf.xml
 [...]


   92.63% (201/217) doc/user/scons_exi.xml
 ERROR: doc/user/scons_exi.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc, {http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4367
 Validation failed! Please correct the errors above and try again.


  Can I remove those sections? I'm not that familiar with the schema.

   The failing files scons_ex.xml and scons_exi.xml are generated
 during the actual build process. Remove them by hand, or do a scons -c
 before trying to validate...

 Regards,

 Dirk


 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev


___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide generation questions

[Mark Flacy]

Do you have a branch/repo I can pull from/clone to see?

I use docbook a lot.

On August 31, 2014 10:51:14 AM CDT, William Blevins wblevins...@gmail.com 
wrote:
That may be a valid problem though because when I run *scons* from #
*doc/user* the index.html generated from the build is completely empty.

V/R,
William


On Fri, Aug 29, 2014 at 6:44 PM, Dirk Bächle tshor...@gmx.de wrote:

  On 30.08.2014 00:12, William Blevins wrote:

 I am trying to make some misc updates to the User Guide, and I am
having
 some issues. I thought it might be a problem with a document do I
tried
 docs-validate and there were two errors:

  [...]


   81.11% (176/217) doc/user/scons_ex.xml
 ERROR: doc/user/scons_ex.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is
one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc,
{http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4116
 81.57% (177/217) doc/user/sconf.xml
 [...]


   92.63% (201/217) doc/user/scons_exi.xml
 ERROR: doc/user/scons_exi.xml fails to validate:
 Element 'programlisting': This element is not expected. Expected is
one
 of ( {http://www.scons.org/dbxsd/v1.0}refentry.class, {
 http://www.scons.org/dbxsd/v1.0}refentry, {
 http://www.scons.org/dbxsd/v1.0}section.class, {
 http://www.scons.org/dbxsd/v1.0}section, {
 http://www.scons.org/dbxsd/v1.0}toc,
{http://www.scons.org/dbxsd/v1.0}lot,
 {http://www.scons.org/dbxsd/v1.0}index, {
 http://www.scons.org/dbxsd/v1.0}glossary, {
 http://www.scons.org/dbxsd/v1.0}bibliography, {
 http://www.scons.org/dbxsd/v1.0}simplesect )., line 4367
 Validation failed! Please correct the errors above and try again.


  Can I remove those sections? I'm not that familiar with the schema.

   The failing files scons_ex.xml and scons_exi.xml are generated
 during the actual build process. Remove them by hand, or do a scons
-c
 before trying to validate...

 Regards,

 Dirk


 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev






___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide generation questions

[Dirk Bächle]

William,

On 31.08.2014 19:50, William Blevins wrote:
This is happening from a clean scons checkout with no local changes. 
 I am currently at revision 3187:605ae0a39155.  I assume this is also 
an issue in default latest.


Using python 2.6 on a RHEL6 or equivalent linux distro.

I'm currently at revision 3189:98dea26fbc96 and I can build the docs 
just fine. My working directory is #doc/user and I call


  python ../../src/script/scons.py

. Please ensure that you have the following Python bindings on your 
system libxml2+libxslt or lxml.


Regards,

Dirk


V/R,
William


On Sun, Aug 31, 2014 at 12:56 PM, Mark Flacy mfl...@verizon.net 
mailto:mfl...@verizon.net wrote:


Do you have a branch/repo I can pull from/clone to see?

I use docbook a lot.


On August 31, 2014 10:51:14 AM CDT, William Blevins
wblevins...@gmail.com mailto:wblevins...@gmail.com wrote:

That may be a valid problem though because when I run
*scons* from #*doc/user* the index.html generated from the
build is completely empty.

V/R,
William



___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide generation questions

[William Blevins]

 python ../../src/script/scons.py
 Please ensure that you have the following Python bindings on your system
 libxml2+libxslt or lxml.


I have *python-lxml-2.2.3-1* installed.

I tried *python ../../src/script/scons.py* with both python 2.6 and python
2.7 with the same results (from what I could tell).  There is an index.html
in *#doc/user* that has been committed but it doesn't seem to update, and
the index.html inside *#doc/user/scons-user* is empty (size 0 bytes).

I was able to generate these files correctly (I assume) when I updated docs
for Issue2395, but my baseline was probably from a month ago or longer.

V/R,
William


On Sun, Aug 31, 2014 at 3:08 PM, Dirk Bächle tshor...@gmx.de wrote:

  William,


 On 31.08.2014 19:50, William Blevins wrote:

 This is happening from a clean scons checkout with no local changes.  I am
 currently at revision 3187:605ae0a39155.  I assume this is also an issue in
 default latest.

  Using python 2.6 on a RHEL6 or equivalent linux distro.

   I'm currently at revision 3189:98dea26fbc96 and I can build the docs
 just fine. My working directory is #doc/user and I call

   python ../../src/script/scons.py

 . Please ensure that you have the following Python bindings on your system
 libxml2+libxslt or lxml.

 Regards,

 Dirk


  V/R,
 William


 On Sun, Aug 31, 2014 at 12:56 PM, Mark Flacy mfl...@verizon.net wrote:

 Do you have a branch/repo I can pull from/clone to see?

 I use docbook a lot.


 On August 31, 2014 10:51:14 AM CDT, William Blevins 
 wblevins...@gmail.com wrote:

 That may be a valid problem though because when I run *scons* from #
 *doc/user* the index.html generated from the build is completely empty.

  V/R,
 William



 ___
 Scons-dev mailing list
 Scons-dev@scons.org
 http://two.pairlist.net/mailman/listinfo/scons-dev


___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev

Re: [Scons-dev] User Guide generation questions

[Dirk Bächle]

On 30.08.2014 00:12, William Blevins wrote:
I am trying to make some misc updates to the User Guide, and I am 
having some issues. I thought it might be a problem with a document do 
I tried docs-validate and there were two errors:


[...]




81.11% (176/217) doc/user/scons_ex.xml
ERROR: doc/user/scons_ex.xml fails to validate:
Element 'programlisting': This element is not expected. Expected
is one of ( {http://www.scons.org/dbxsd/v1.0}refentry.class
http://www.scons.org/dbxsd/v1.0%7Drefentry.class,
{http://www.scons.org/dbxsd/v1.0}refentry
http://www.scons.org/dbxsd/v1.0%7Drefentry,
{http://www.scons.org/dbxsd/v1.0}section.class
http://www.scons.org/dbxsd/v1.0%7Dsection.class,
{http://www.scons.org/dbxsd/v1.0}section
http://www.scons.org/dbxsd/v1.0%7Dsection,
{http://www.scons.org/dbxsd/v1.0}toc
http://www.scons.org/dbxsd/v1.0%7Dtoc,
{http://www.scons.org/dbxsd/v1.0}lot
http://www.scons.org/dbxsd/v1.0%7Dlot,
{http://www.scons.org/dbxsd/v1.0}index
http://www.scons.org/dbxsd/v1.0%7Dindex,
{http://www.scons.org/dbxsd/v1.0}glossary
http://www.scons.org/dbxsd/v1.0%7Dglossary,
{http://www.scons.org/dbxsd/v1.0}bibliography
http://www.scons.org/dbxsd/v1.0%7Dbibliography,
{http://www.scons.org/dbxsd/v1.0}simplesect
http://www.scons.org/dbxsd/v1.0%7Dsimplesect )., line 4116
81.57% (177/217) doc/user/sconf.xml
[...]




92.63% (201/217) doc/user/scons_exi.xml
ERROR: doc/user/scons_exi.xml fails to validate:
Element 'programlisting': This element is not expected. Expected
is one of ( {http://www.scons.org/dbxsd/v1.0}refentry.class
http://www.scons.org/dbxsd/v1.0%7Drefentry.class,
{http://www.scons.org/dbxsd/v1.0}refentry
http://www.scons.org/dbxsd/v1.0%7Drefentry,
{http://www.scons.org/dbxsd/v1.0}section.class
http://www.scons.org/dbxsd/v1.0%7Dsection.class,
{http://www.scons.org/dbxsd/v1.0}section
http://www.scons.org/dbxsd/v1.0%7Dsection,
{http://www.scons.org/dbxsd/v1.0}toc
http://www.scons.org/dbxsd/v1.0%7Dtoc,
{http://www.scons.org/dbxsd/v1.0}lot
http://www.scons.org/dbxsd/v1.0%7Dlot,
{http://www.scons.org/dbxsd/v1.0}index
http://www.scons.org/dbxsd/v1.0%7Dindex,
{http://www.scons.org/dbxsd/v1.0}glossary
http://www.scons.org/dbxsd/v1.0%7Dglossary,
{http://www.scons.org/dbxsd/v1.0}bibliography
http://www.scons.org/dbxsd/v1.0%7Dbibliography,
{http://www.scons.org/dbxsd/v1.0}simplesect
http://www.scons.org/dbxsd/v1.0%7Dsimplesect )., line 4367
Validation failed! Please correct the errors above and try again.


Can I remove those sections? I'm not that familiar with the schema.

The failing files scons_ex.xml and scons_exi.xml are generated 
during the actual build process. Remove them by hand, or do a scons -c 
before trying to validate...


Regards,

Dirk

___
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev