Remove forcefield from data package after it is made installable on other repo

[davidlmobley]

This PR included a version of the forcefield in the data package which is installed here: #203

A better long-term solution is to make the versioned forcefield itself conda-installable. openforcefield/smirnoff99Frosst#13

[bmanubay]

Hey @davidlmobley,

Just to clarify: there is currently no way to load an ffxml with smarty unless it is in the proper data directory on your os.path, correct? Michael and I were discussing how it would be convenient if the ffxml could be loaded locally, or if the file was conda-installable into the proper directory in smarty.

[davidlmobley]

@bmanubay -- right now, what you are saying is correct if you're after loading an ffxml from within the repo. Of course if you provide your own ffxml you can load it. :)

However, the latest master now includes the main smirff99frosst.ffxml in its data directory so it gets installed -- see #203 . As soon as we cut a new release and update the conda recipe (which might or might not be very soon depending on whether this is important to you) it would be conda installable, at least temporarily (cc @nathanmlim ).

See also the other issues cross-linked there, as this is not the best long-term solution.

Is that clear? Sorry, I'm rushing.

[bmanubay]

Crystal clear David! Having smirff99frosst.ffxml in the latest smarty version will suffice just fine for now, but I do agree that having the ffxml files be conda-installable would be AWESOME from a more collaborative development standpoint :)

[davidlmobley]

@bmanubay - see tentative plan here: openforcefield/smirnoff99Frosst#13

If this is something which becomes more urgent for you please comment again.