Bug 695609 - libXaw documentation is in source form only
Summary: libXaw documentation is in source form only
Status: RESOLVED WONTFIX
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.4
: P5 - None : Normal with 1 vote (vote)
Target Milestone: ---
Assignee: Forgotten User Wum0mkMcd8
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 07:52 UTC by Christopher Yeleighton
Modified: 2011-05-24 13:13 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2011-05-24 07:52:38 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

The documentation included in xorg-x11-devel is in source form only (DocBook).
 It is not directly readable and no instruction is provided on how to read it.

Reproducible: Always

Steps to Reproduce:
  1. { rpm '-qd' 'xorg-x11-devel' | grep '-F' 'libXaw'; }
  2. { xdg-open /usr/share/doc/libXaw/libXaw.xml; }
Actual Results:  
  1. XML (DocBook) and SVG files.
  2. 
Results vary; at best, XML source; 
at worst, an unreadable interpretation in Konqueror (KDE Bug 239979).



Expected Results:  
Expected Results:  
  1. Something directly readable, e.g. HTML.

Useful documentation can be generated using xmlto but xmlto is a build time tool; it does not accompany X11.  And you will end up with multiple identical generated copies for each user if you do not install readable documentation as a package.
Comment 1 Stefan Dirsch 2011-05-24 08:54:23 UTC 
Please not again. We had enough trouble with the build cycles you've introduced.
Comment 2 Christopher Yeleighton 2011-05-24 09:59:15 UTC 
Not again what?  It is best not to have a bug; failing that, the bug should be fixed; failing that, the bug should be described.
What build cycles have I introduced?  I did not introduce the xmlto cycle and I do not know of any other ones.
Comment 3 Stefan Dirsch 2011-05-24 10:22:01 UTC 
> What build cycles have I introduced?  I did not introduce the xmlto cycle and I
> do not know of any other ones.

Of course you did. I needed to revert your changes.
Comment 4 Christopher Yeleighton 2011-05-24 11:32:01 UTC 
I asked you twice to postpone accepting my request until the request for xmlto is accepted.  My build did not introduce the cycle because it relied on modified xmlto.
Comment 5 Stefan Dirsch 2011-05-24 11:55:14 UTC 
No idea what you're talking about. Why are you making submitrequests knowing that it is going to break the distribution without having other things changed first, which may never happen ...
Comment 6 Christopher Yeleighton 2011-05-24 13:13:28 UTC 
I submitted the package conditionally hoping that it would serve as an incentive to update xmlto.  Sorry it did not work out.
I think a Build Service infrastructure where requests could explicitly depend on each other would be very helpful.