On 6.10.2014 23:40, Fernando de Oliveira wrote:
On 06-10-2014 17:59, Armin K. wrote:
There is no need to invert it. It was done like this because if someone
does rm -rf /usr/share/doc/* (it can take a lot of space, so there's a
good chance for that) that CUPS web interface remains in tact, because
it's installed in docdir. symlink is created to honor the traditional
docdir. You don't need the reverse symlink, but you have a risk of
losing the web interface.
Problem is that, when/if updating, it will mix previous and new docs,
but the versioned symlinks will point to the same directory. So,
installing in versioned directories, and symlinking would make sure that
different versions will have different directories and the symlink will
point to the newest one.
Yeah, you got that right. Still, the docdir is actually a document root
for CUPS web interface - it contains no docs that could be read directly
by an end user - but could be from the CUPS web interface.
The reason why it was moved was already explained - as a safeguard from
rm -rf /usr/share/doc/* (which I got burned by) where you'd lose CUPS
web interface.
Still, the second part stands (that's not part of this reply) is that
the symlink to /usr/share/cups/doc isn't needed if done this way - but
then again if you decide to keep it this way it would be a good idea to
add a note to the CUPS page that the docdir and its contents shouldn't
be deleted, something like:
"The /usr/share/doc/cups-<version> directory contains HTML documents for
the CUPS web interface and it is important that it doesn't get deleted."
(Feel free to improve the wording).
The another solution is to install a versioned dir into /usr/share/cups,
ie /usr/share/cups/doc-2.0.0 so the old symlinks always point to the
versioned document root outside of /usr/share/doc.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
