Missing COPYING file about flex-compiler-shell-daemon HOT 5 OPEN

Patches are welcomed. I'd apply it right away.

This is a bit tricky.

The daemon code that you are using is from
<http://code.activestate.com/recipes/278731/>

That website says that the license is PSF (Python Software Foundation).

The PSF actually recommends against using their license: "Many projects on 
Source Forge and elsewhere have adopted the PSF license, but not always in an 
appropriate way"
<http://wiki.python.org/moin/PythonSoftwareFoundationLicenseFaq#How_do_I_use_the
_PSF_License.3F>

It's not quite clear to me from the text of the PSF License 
<http://wiki.python.org/moin/PythonSoftwareFoundationLicenseV2Easy> how to 
properly comply with it, especially since the wording is specific to the Python 
project and the Python Software Foundation, instead of in this case the real 
copyright holder.

The best thing would be to ask the author if he could additionally license the 
code under BSD(which pretty much has the same spirit as the PSF), but I can't 
find his email.

Would relicensing fcshd under the PSF License fix the issue?

No, I don't think relicensing fcsh under the PSF License would help here.

I'll try working on a patch that adds the BSD license header to fcshd.py and 
also acknowledges the copyright and licensing terms of the daemon python recipe.

Related issue: Which exact BSD license is your intention for fcsh? The Google 
Code project information lists "New BSD License", which is commonly meant to 
refer to the 3-clause BSD license, but the link actually points to the 
"Simplified" 2-clause BSD license.

There is an open issue with Google Code about this:
<http://code.google.com/p/support/issues/detail?id=5543>

Could you please clarify whether fcsh is licensed under the 2-clause or 
3-clause BSD?

Thanks

I personally prefer the 3-clause BSD license. So that would be my original 
intention.