Package: bash
Version: 4.1-3
Followup-For: Bug #427804

Please ditto, "me too", nag nag, 4th aniversary, etc.

Of course the bigger problem is not just 'bash'.  Someday there needs
to be a general solution for problems with unavailable "nonfree" 'info'
files. For example, many Debian 'man' pages recommend 'info' files,
that in Debian haven't been available in (four) years.  Because of such
obsolete manual references, thousands of Debian users regularly
discover such wild goose chases.

Beyond that a more general problem: we have software package dependency
checking, and we have kernel bootup/hardware/init dependency checking,
but no general documentation dependency checking.  We might start by
never documenting a file that's not there.  Therefore there'd need to
be some kind of metadata in or about docs, dating and versioning 
references to specific files, programs, switches, menu locations, and
features -- then whenever there's a location or name change to a file,
the hypothetical documentation dependency checker would automatically
either flag or correct the error.

HTH...

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

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

Versions of packages bash depends on:
ii  base-files                   6.3         Debian base system miscellaneous f
ii  dash                         0.5.5.1-7.4 POSIX-compliant shell
ii  debianutils                  3.4.4       Miscellaneous utilities specific t
ii  libc6                        2.13-2      Embedded GNU C Library: Shared lib
ii  libncurses5                  5.9-1       shared libraries for terminal hand

Versions of packages bash recommends:
ii  bash-completion               1:1.3-1    programmable completion for the ba

Versions of packages bash suggests:
ii  bash-doc                      4.1-3      Documentation and examples for the

-- debconf-show failed



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to