mime.types.conf int lighttpd

Elan Ruusamäe glen at pld-linux.org
Tue Mar 20 17:40:21 CET 2012

On 20.03.2012 18:34, Paweł Gołaszewski wrote:
> On Tue, 20 Mar 2012, Elan Ruusamäe wrote:
>>>>> [...]
>>>>> Are you going to fix it? It's quite long time....
>>>> i was waiting your reply to my question...
>>>> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2012-February/022491.html
>>>> followed further discussion/explanation, but no real reply to
>>>> question!
>>> I don't want to argue - I just want to have it *working* again. You broke,
>>> you fix. I don't know the internals and I don't want to know.
>>> Fix it or revert your previous change.
>> i proposed a solution, is that fix acceptable?
> Will it destroy _working_ configurations?
> If "yes" (IMvHO it's the case) then - it's not acceptable.
new %config(noreplace) is deployed as .rpmnew, so no, if you made 
changes to that file
> If this that option is apaches "add default charset" equivalent - you have
> anwer from me and baggins.
it's equivalent yes, so same issues are present there
> What is the _rationale_ for that change?

utf-8 as default encoding, to all documents. there's no way specify 
encoding as html tag for .txt files

> What more do you want to know??

i wanted to know is that change acceptable, or you still find that me 
breaking your window and violating your cat.


More information about the pld-devel-en mailing list