For quite some time I have been trying to get the package distributors to handle our mime.conf file as a Squid-specific config file, which gets FHS $(sysconf) installation instead of a Squid a data file, which gets FHS $(datadir) installation.
But there are still some strong holdouts for a couple of reasons... * some simply do not get the idea that something called mime.conf can be completely different in purpose from mime.conf / mime.table provided by the OS for file type sniffing. These ones are mapping our mime.conf to that table and screwing over the FTP and Gopher directory listings. (Thankfully it is not the OS getting screwed over). * some are having issues with our mime.conf clashing with the system one in their automated system install/uninstall tools and QA systems. It has been a long battle and I think we have reached a stalemate where I cannot do much more than just rename the file and avoid both these confusions. Are there any objections to renaming mime.conf to icons.conf ? Or suggestions of a better file name for it ? Amos
