-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate with boost-cpp #53
Comments
To avoid having the same discussion twice, would you be alright closing this and continuing in issue ( conda-forge/boost-cpp-feedstock#25 )? |
I'd rather not close this issue until a decision has explicitly been made
to either merge recipes or keep them split. I agree that no further
discussion should occur on this particular issue, all discussion should
happen at conda-forge/boost-cpp-feedstock#25 and we should lock this issue
to enforce that.
On Wednesday, April 18, 2018, jakirkham ***@***.***> wrote:
To avoid having the same discussion twice, would you be alright closing
this and continuing in issue ( conda-forge/boost-cpp-feedstock#25 )?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.<
|
Closed by #164 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The AnacondaRecipes version of this feedstock (https://github.com/anacondarecipes/boost-cpp-feedstock) incorporates boost-python and libboost, as well as "boost" and "boost-cpp" as metapackages. As part of the unification with defaults, we should discuss how to deprecate this repo and have only one boost feedstock that has the package splitting.
The text was updated successfully, but these errors were encountered: