conda install removes fortran codes?

[rjleveque]

@ketch: I got the conda install to work so that I can import the python codes, but it seems to install these in the ~/anaconda/envs/.../lib/python2.7/site-packages and remove the source. Your email to claw-users about this indicated that this was a good way for users of classic, amrclaw, etc. to install without worrying about f2py choking, but how do you access any of those codes?

[ketch]

It definitely cloned the fortran codes during the build process. I don't understand conda very well. I will try to figure this out.

[ketch]

I'm seeing the same behavior you describe. Sorry for not testing more thoroughly.

There must be a way to force conda to copy specific files into the build, but it's surprisingly difficult to figure out. Of course, the way GeoClaw/AMRClaw/etc. are distributed (copying source) is just what Conda was built to avoid, so perhaps this is not surprising.

[dalcinl]

Folks, conda packages whatever setup.py installs. Maybe you should specify package_data in the call to setup() within the setup.py script.