Re: "textual binary" MIME types (was Re: file locking and binary files)

Greg Hudson <ghudson@MIT.EDU> writes:

> I disagree with both of you. This isn't configuration data,
> this is information. No one has an interest in configuring
> whether image/x-xbitmap is composed of text or not. They may
> have an interest in adding application/x-localtype, but that
> doesn't turn the contents of the default list into
> configuration data.

You contradict yourself. First you say the list is not
configuration data, then you say the list should be configurable.
The list *is* configuration data; like most configuration data,
it has a set of defaults. If you want to have the defaults in
the code, that is fine, i will not argue against that. But, you
can also have the defaults simply be the default state of the
file. Not having the file at all is a problem, but like i said,
a problem people can accept in a 1.0 release.

> The "magic" file used by the Unix file command is a good analog.

Not really. Hard-coding the list into the file bianry would be a
good analog. Is /usr/share the right place for the file?
Possibly. At least the file exists.

--
Eric Gillespie <*> epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 18 20:10:05 2002