[cups.general] CUPS documentation and web content at the same place

[Michael Sweet]

On May 5, 2010, at 2:55 AM, Johannes Meixner wrote:
>> ...
>> Instead, why not just do:
>>   %doc /path/to/webcontent/help
>> since all of the online help is stored in the "help" subdirectory?
> 
> This could be a possible solution for plain RPM but then
> the parent directory /path/to/webcontent must be no longer
> one of the well known RPM documentation directories
> because the non-help CUPS web content files are
> no documentation files.

Well, there is 1 file (index.html) that is not strictly a documentation file but *does* provide links to popular documentation files.

> In this case I would have to do
>   ./configure --with-docdir=/non/documentation/directory
> where /non/documentation/directory is something like
> $(cups-config --datadir) or $(cups-config --serverbin)
> i.e.
>   ./configure --with-docdir=/usr/share/cups/webcontent
> or
>   ./configure --with-docdir=/usr/lib/cups/webcontent
> depending on whether or not the CUPS web content files
> are actually shareable between different machines of possibly
> different hardware architecture (e.g. 32-bit versus 64-bit)
> but with the same version of CUPS installed according to
> http://www.pathname.com/fhs/pub/fhs-2.3.html#USRSHAREARCHITECTUREINDEPENDENTDATA

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

> I think that the CUPS web content files are actually shareable
> in this way (I never got a bug report regarding our current
> web content location /usr/share/doc/packages/cups)
> so that I would prefer
>   ./configure --with-docdir=/usr/share/cups/webcontent
> 
> But this is contradicting to what "./configure --help" shows:
> --------------------------------------------------------------------
>   --with-docdir    set path for documentation
> --------------------------------------------------------------------
> 
> It would be also no longer in compliance to the CUPS upstream
> default location of the web content according to
> http://www.cups.org/documentation.php/doc-1.4/ref-cupsd-conf.html

That's been the case on several Linux distros already, and the local content will always show the correct values.

> ...
> I think that all what might be changed is only the configure
> option name  "--with-docdir" to something which matches
> its actual usage e.g. to "--with-web-content-dir".

I am loath to changing the configure option after 11 years of use.

> ...
> Michael,
> would you mind if I use now in the Novell/openSUSE CUPS RPMs
>   ./configure --with-docdir=%{_datadir}/cups/webcontent
> or should I better wait until you changed the CUPS upstream
> default location of the web content?

The cups.org 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.

> May I file an enhancement request for CUPS 1.5 regarding the issue?

You can, but I'm not really sure at this point what the changes (if any) would be.

________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20100505/3415f28f/attachment-0001.html>