From: deskpot@despammed.com (Vasily Korytov)
Subject: Re: multiple mailcap entries
Date: Sat, 12 Apr 2003 20:27:27 +0400 [thread overview]
Message-ID: <873ckn8yvk.fsf@unix.home> (raw)
In-Reply-To: <i7he9396e8.fsf@hilbert.math.albany.edu>
On 12 Apr 2003 09:45:03 -0400, William F. Hammond wrote:
> Aren't /etc and /usr/etc generally are regarded as being for vendor
> defaults, while /usr/local/etc is for system defaults? If so,
> shouldn't /usr/local/etc be higher in these lists?
[...]
I have never heard of such a convention. IIRC, FHS doesn't mention
/usr/(local/)?/etc at all.
IMHO, if I have both /usr/local/etc/aa.conf and /etc/aa.conf, that's
wrong by itself and I shouldn't care much about the sequence.
The reason to have /etc/mailcap before /usr/local/etc/mailcap is: it's
more standard and frequently used.
--
I accept RFC3156 and RFC2440-compatible encrypted mail.
PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841
next prev parent reply other threads:[~2003-04-12 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 13:10 Klaus Zeitler
2003-04-09 14:52 ` Jesper Harder
[not found] ` <84k7e16o11.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <m3d6jseslm.fsf@defun.localdomain>
[not found] ` <84znmw7ov2.fsf@lucy.is.informatik.uni-duisburg.de>
2003-04-11 20:58 ` Jesper Harder
[not found] ` <q5gsmspnnmr.fsf@lucent.com>
[not found] ` <m3fzooesro.fsf@defun.localdomain>
[not found] ` <i7he9396e8.fsf@hilbert.math.albany.edu>
[not found] ` <m3adevu7il.fsf@defun.localdomain>
[not found] ` <84brzbvj0v.fsf@lucy.is.informatik.uni-duisburg.de>
2003-04-12 15:32 ` Adam Sjøgren
2003-04-12 16:21 ` Vasily Korytov
2003-04-12 16:27 ` Vasily Korytov [this message]
2003-04-14 6:38 ` Arne Jørgensen
[not found] ` <85istme3yw.fsf.Hubert.Canon@alussinan.org>
[not found] ` <m3r88a8i6c.fsf@defun.localdomain>
2003-04-11 10:53 ` Gnus and indentation Hubert Canon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873ckn8yvk.fsf@unix.home \
--to=deskpot@despammed.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).