Greg Hudson wrote:
> On Mon, 2002-11-18 at 12:59, Eric Gillespie wrote:
>
>>Hard-coding configuration data (yes, that's what it is) in your
>>code is generally considered a bad idea.
>
...
> The "magic" file used by the Unix file command is a good analog. It can
> never be complete because people create new file formats, so you want it
> to be easily updated, but it's not configuration. It generally lives in
> /usr/share/magic on modern systems. You could imagine allowing an
> /etc/localmagic where people could add magic for local file formats, but
> it doesn't look like file supports that (and I don't think anyone really
> cares).
Not that we have to do it the CVS way, but I recall a file in
/<cvsroot>/CVSROOT that held patterns for binary file names (I'd go look it up
but I've already deleted my last CVS install. :-) Anyway, why couldn't we do
somthing like that? OK, it'd probably list mime-types instead of file
extensions, but it should work.
I'm sure that's what's floating around in the idea above, but I thought I'd
mention the CVS remedy, so we can steal an idea if need be. (Maybe make the
list a repository property?)
HTH,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 18 22:44:12 2002