Armin K. wrote: > In LFS and BLFS we use package-package-version for docdir, eg > /usr/share/doc/attr-2.4.46. Why? I mean, it is somehow stupid if you ask > me. If you keep your system arround for some time, and upgrade such > packages, you will have dozen of versioned directories in there. But > that's not all. There are lot of packages that just install their > documentation in non-versioned directory, especially Xorg stuff. So in > the end, we have half of packages with versioned docdir and half with > non-versioned. So, which one to keep? Which one would suit us better?
I'm not sure how that started, but it's to identify the version of the package. It one version has doc1 and doc2, a second version may drop doc1 and add doc3. It's a crude form of version control, but one we've been doing a long time. Personally, if I did rm -r /usr/share/doc, I don't think I'd miss it very often. Looking at my older system, I have some docs that go back to vim-6.4, hal-0.5.4, imlib2-1.2.2, xmms-1.2.10, etc. The whole directory is 369M, so it uses some space, but then again, it's only 3% of my 10G directory. On my recent system it's 126M. I don't see a lot of non-versioned docs. Only check, lame, pkg-config, speex, sudo, and udev-config. It would be easier to change those than to remove the version everywhere else. It's a bit more of a mixtue on /usr/share. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
