Andreas Metzler <[EMAIL PROTECTED]> writes: >> The *-doc packages are good for learning, but building up a simple >> system with as few packages as possible is easier if the documentation >> and the running binaries are separated. It is not absolutely necessary >> to have the documentation once you have used lynx. > > Hello, > That applies for every single piece of documentation we ship, > including manpages.
Manual pages are special case. A standard system contains binaries + configuration files + manual pages. >> ... N x N extra documentation to take up the room. > >> The plea was to separate the documentation and have it listed in >> "Recommends:". > > For real tight situations you could just execute > "rm -rf /usr/share/doc/*" after every dpkg run (and wait for > http://bugs.debian.org/68861 to get a real solution.) All is possible of course, but the ideal would be to use the package manager for all tasks. Manual interventions are not easily re-creatable/remembered when re-installed. > Splitting off additional packages is not without cost. Growth of the > package count slows down dpkg/apt by increasing the size of the > status file and making dependencies more complicated. Winning 500KB > but shipping lynx without (imho necessary) documentation and needing > another package The cost is, I believe, minor like in debian/control. The package manager also can handle the dependencies given the fields Suggests, Recommends etc. The split is usually good thing in many cases to separate extra documentation (other than manual pages) from the running binaries. I'm just hoping to see the change in this case. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
