DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I installed Lenny on a new system and there are almost no info files installed. I was trying to look up the "tar" manual. The man page indicates that the real docs are in the info file. But the info file isn't installed! I hunted around for a while thinking maybe the manuals were installed in a different format, but I can't seem to find them. Where are they?
The GNU folks, in general, abhor man pages, and create info documents
instead. Unfortunately, the info document describing tar is licensed
under the GFDL with invariant cover texts, which violates the Debian
Free Software Guidelines. As a result, the info documentation for tar
is not included in the Debian package.
Mine says this. No explanation about how the documentation is missing because of some obscure disagreement over licensing issues.
Code:
The GNU folks, in general, abhor man pages, and create info documents
instead. The maintainer of tar falls into this category. This man
page is neither complete, nor current, and was included in the Debian
Linux packaging of tar entirely to reduce the frequency with which the
lack of a man page gets reported as a bug in our defect tracking sys-
tem.
If you really want to understand tar, then you should run info and read
the tar info pages, or use the info mode in emacs.
I find it fantastically, incredibly, unbelievably annoying to be referred to a web page for manuals. (The netpbm utilities have annoyed me to no end for having cut the manuals.) For one thing, this means I'm unlikely to be reading the manual that goes with my version of the software. What if I'm not on line and need to consult a manual? I mean, renaming firefox to iceweasel doesn't really cause any trouble, but NOT INSTALLING THE MANUALS??? That's ridiculous. Is there some fix to get the manuals properly installed?
That's ridiculous. Is there some fix to get the manuals properly installed?
Easy. Use some distribution other than Debian. Whoever wrote the manuals elected to distribute them under a non-free license. Debian does not distribute non-free software or documentation.
I must admit that it seems a little crazy that GNU isn't considered free enough for Debian. How could anybody expect something like this going in.
But installing "tar-doc" from the non-free repository sounds like the solution I was seeking. Is there a reasonable way to install all the missing documentation as opposed to having to do it piecemeal one program at a time? I mean, I could try to install X-doc for every package X that is installed on my system, I suppose.
I'm not aware of any easy way to install the documentation for all installed packages. Hopefully, someone here with stronger apt-foo then I will be able to answer that.
I must admit that it seems a little crazy that GNU isn't considered free enough for Debian.
LOL. Welcome to the world of Debian.
Quote:
Is there a reasonable way to install all the missing documentation as opposed to having to do it piecemeal one program at a time?
I asked a similar question a while ago regarding pulling in -dev/-devel packages. It seems at present, there is no easy way to do it. It would be nice if packages declared their -doc -dev -dbg packages explicitly. Then apt would be able to handle things with ease. But at this point in time, they don't. Perhaps down the line Debian policy may change, but for the moment, it's a matter of finding and installing them manually.
Yes, coming from OpenSUSE I was also surprised that the doc installation is often separate on Debian.
Just doing aptitude search doc and aptitude search html will get you lists of available documentation in several formats and languages.
An easier way might be using just aptitude and then you'll see the documentation category of each of the sections.
Or, open synaptic and you can also browse there. But I just use synaptic for browsing and then close it when I know what I want and install it through aptitude on the command line.
It's all there (assuming you added the sources to the sources.list file.) If you like, you can work with that file through Synaptic or Software Sources (same thing).
I've seen that Debian offers just about the entire Open Source library of software. Way more than most other distro's. However even running testing we get to wait a bit for upgrades. I like that when I see forum posts in other distro's forums about how come this or that doesn't work properly, or has broken something on their system.
And then there's the very strict adherence to their principals. But I wind up liking that too, as long as I can still find a way to fulfill whatever it is I need to do with the computer. And with the vast assortment of software and easy installation and configuration (dpkg-reconfigure, update-alternatives, etc.) there's nearly always a way.
The most adaptable to a users needs I've seen from any distro.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.