Your message dated Sat, 26 Jan 2008 16:01:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Please give dircolors a configration file instead of
compiled-in defaults
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: coreutils
Version: 5.2.1-2.1
Severity: wishlist
File: /usr/bin/dircolors
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
It seems right now that if I want to change system-wide defaults for
dircolors, I must download coreutils source, patch it, and install the
modified version. As changing the dircolors database seems like a
perfectly reasonable thing for the sysadmin to want to do, this really
should be a configuration file.
- -- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (130, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-k8-smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages coreutils depends on:
ii libacl1 2.2.32-1 Access control list shared library
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
coreutils recommends no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDd2o3+z+IwlXqWf4RAkHDAKCNPkwSvaj3MnbjtnLpjnWtPPUvBACfUXDb
ss8dO4nEcS3SbaGFx5VXOxg=
=OpKA
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
I think that the functionality is basically there; you can give
dircolors a configuration file as a parameter, and that can be used to
set the environment. Someone seems to have broken this by overriding the
default environment in the default .bashrc, but that's not something I
can fix from the coreutils package.
Mike Stone
--- End Message ---