<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 5, 2010, at 2:55 AM, Johannes Meixner wrote:</div><blockquote type="cite"><div><blockquote type="cite"><font class="Apple-style-span" color="#000000">...</font></blockquote></div></blockquote><blockquote type="cite"><div><blockquote type="cite">Instead, why not just do:<br></blockquote><blockquote type="cite"> %doc /path/to/webcontent/help<br></blockquote><blockquote type="cite">since all of the online help is stored in the "help" subdirectory?<br></blockquote><br>This could be a possible solution for plain RPM but then<br>the parent directory /path/to/webcontent must be no longer<br>one of the well known RPM documentation directories<br>because the non-help CUPS web content files are<br>no documentation files.<br></div></blockquote><div><br></div>Well, there is 1 file (index.html) that is not strictly a documentation file but *does* provide links to popular documentation files.</div><div><br><blockquote type="cite"><div>In this case I would have to do<br> ./configure --with-docdir=/non/documentation/directory<br>where /non/documentation/directory is something like<br>$(cups-config --datadir) or $(cups-config --serverbin)<br>i.e.<br> ./configure --with-docdir=/usr/share/cups/webcontent<br>or<br> ./configure --with-docdir=/usr/lib/cups/webcontent<br>depending on whether or not the CUPS web content files<br>are actually shareable between different machines of possibly<br>different hardware architecture (e.g. 32-bit versus 64-bit)<br>but with the same version of CUPS installed according to<br><a href="http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA">http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA</a><br></div></blockquote><div><br></div>By those rules you'd need to install the files in /usr/lib/cups/foo since several of the help files are tweaked based on what you pass to the configure script (just as the man pages reflect what is passed to configure...)</div><div><br><blockquote type="cite"><div>I think that the CUPS web content files are actually shareable<br>in this way (I never got a bug report regarding our current<br>web content location /usr/share/doc/packages/cups)<br>so that I would prefer<br> ./configure --with-docdir=/usr/share/cups/webcontent<br><br>But this is contradicting to what "./configure --help" shows:<br>--------------------------------------------------------------------<br> --with-docdir set path for documentation<br>--------------------------------------------------------------------<br><br>It would be also no longer in compliance to the CUPS upstream<br>default location of the web content according to<br><a href="http://www.cups.org/documentation.php/doc-1.4/ref-cupsd-conf.html">http://www.cups.org/documentation.php/doc-1.4/ref-cupsd-conf.html</a><br></div></blockquote><div><br></div>That's been the case on several Linux distros already, and the local content will always show the correct values.</div><div><br><blockquote type="cite"><div>...</div></blockquote><blockquote type="cite"><div>I think that all what might be changed is only the configure<br>option name "--with-docdir" to something which matches<br>its actual usage e.g. to "--with-web-content-dir".<br></div></blockquote><div><br></div>I am loath to changing the configure option after 11 years of use.</div><div><br></div><div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">...<br></font>Michael,<br>would you mind if I use now in the Novell/openSUSE CUPS RPMs<br> ./configure --with-docdir=%{_datadir}/cups/webcontent<br>or should I better wait until you changed the CUPS upstream<br>default location of the web content?<br></div></blockquote><div><br></div>The <a href="http://cups.org">cups.org</a> documentation currently reflects the defaults as set on Mac OS X. They already don't match what you ship, so please go ahead and make it whatever you need.</div><div><br></div><div><blockquote type="cite"><div>May I file an enhancement request for CUPS 1.5 regarding the issue?<br></div></blockquote><div><br></div>You can, but I'm not really sure at this point what the changes (if any) would be.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br></body></html>