Your message dated Tue, 12 Aug 2008 16:21:09 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#472192: lynx: please move documentation to lynx-doc 
package
has caused the Debian Bug report #472192,
regarding lynx: please move documentation to lynx-doc package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
472192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472192
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: lynx
Version: 2.8.6-2
Severity: normal


Please separate runtime from the documentation by moving doc/ files to
separate package lynx-doc. The currently files take unnecessary space
on small systems where manual page will suffice:

$ for i in $(dpkg -L lynx | grep doc/); do [ -f $i ] && ls -l $i ; done | awk 
'{sum += $5}END{print sum}'
930962

Current /doc/ files are:

    /usr/share/doc
    /usr/share/doc/lynx
    /usr/share/doc/lynx/lynx_help
    /usr/share/doc/lynx/lynx_help/keystrokes
    /usr/share/doc/lynx/lynx_help/keystrokes/cookie_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/visited_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/edit_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/dired_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/xterm_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/scrolling_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/print_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/other_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/option_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/movement_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/history_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/gopher_types_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/bookmark_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/keystroke_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/follow_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/test_display.html
    /usr/share/doc/lynx/lynx_help/keystrokes/environments.html
    /usr/share/doc/lynx/lynx_help/keystrokes/alt_edit_help.html
    /usr/share/doc/lynx/lynx_help/keystrokes/bashlike_edit_help.html
    /usr/share/doc/lynx/lynx_help/lynx_url_support.html
    /usr/share/doc/lynx/lynx_help/Lynx_users_guide.html
    /usr/share/doc/lynx/lynx_help/lynx_help_main.html
    /usr/share/doc/lynx/lynx_help/about_lynx.html
    /usr/share/doc/lynx/lynx_help/lynx-dev.html
    /usr/share/doc/lynx/lynx_help/help_files.txt
    /usr/share/doc/lynx/FM.announce.gz
    /usr/share/doc/lynx/README.chartrans.gz
    /usr/share/doc/lynx/PROBLEMS.gz
    /usr/share/doc/lynx/README.gz
    /usr/share/doc/lynx/jumpsUnix.html.gz
    /usr/share/doc/lynx/cernrules.txt.gz
    /usr/share/doc/lynx/lynx-keymaps.gz
    /usr/share/doc/lynx/copyright
    /usr/share/doc/lynx/test
    /usr/share/doc/lynx/test/ALT88592.html
    /usr/share/doc/lynx/test/ISO_LATIN1_test.html
    /usr/share/doc/lynx/test/README.txt
    /usr/share/doc/lynx/test/TestComment.html
    /usr/share/doc/lynx/test/c1.html
    /usr/share/doc/lynx/test/iso-8859-1.html
    /usr/share/doc/lynx/test/iso-8859-2.html
    /usr/share/doc/lynx/test/koi8-r.html
    /usr/share/doc/lynx/test/quickbrown.html
    /usr/share/doc/lynx/test/raw8bit.html
    /usr/share/doc/lynx/test/sgml.html
    /usr/share/doc/lynx/test/spaces.html
    /usr/share/doc/lynx/test/special_urls.html
    /usr/share/doc/lynx/test/tabtest.html
    /usr/share/doc/lynx/test/tags.html
    /usr/share/doc/lynx/test/test-styles.html
    /usr/share/doc/lynx/test/unicode.html
    /usr/share/doc/lynx/test/utf-8-demo.html
    /usr/share/doc/lynx/README.Debian.gz
    /usr/share/doc/lynx/changelog.gz
    /usr/share/doc/lynx/CRAWL.announce.gz
    /usr/share/doc/lynx/changelog.Debian.gz


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash

Versions of packages lynx depends on:
ii  libbz2-1.0             1.0.4-3           high-quality block-sorting file co
ii  libc6                  2.7-8             GNU C Library: Shared libraries
ii  libgnutls13            2.0.4-3           the GNU TLS library - runtime libr
ii  libncursesw5           5.6+20080203-1    Shared libraries for terminal hand
ii  zlib1g                 1:1.2.3.3.dfsg-11 compression library - runtime

Versions of packages lynx recommends:
ii  mime-support                  3.40-1     MIME files 'mime.types' & 'mailcap

-- no debconf information



--- End Message ---
--- Begin Message ---
Thomas Dickey <[EMAIL PROTECTED]> writes:

> On Mon, Aug 11, 2008 at 01:00:10AM +0200, Jari Aalto wrote:
>> Atsuhito Kohda <[EMAIL PROTECTED]> writes:
>> 
>> > Hi Jari,
>> >
>> > On Thu, 31 Jul 2008 13:22:09 +0300, Jari Aalto wrote:
>> >
>> >> 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.
>> >
>> > For lynx its documents are setted as HELPFILE in its
>> > configuration file (lynx.cfg) and should be displayed
>> > with key "?" so I guess it is not worth while to separate
>> > its documentation.
>> 
>> You mean that the "?" key requires the documentation. Ahem, I see. In
>> that case I retreat my request, because there nothing that can be
>> done.
>
> technically it could be done by making lynx's configuration point to
> an external machine (but that's probably not a good idea).

I agree. Closing.

Thank you for all the discussers,
Jari


--- End Message ---

Reply via email to