Mahogany license can be changed if it turns out to be a problem. No
developer attempts to "own" the package.

It is worse with c-client library. It is distributed under license similar
to Pine and it must be statically linked to Mahogany. I doubt that
University of Washington is willing to switch license and Mahogany without
c-client is meaningless.

I would like to see this package in Debian, but I must prevent
disappointment when somebody discovers the c-client problem.


Reply via email to