Closed pradal closed 6 years ago
This possibility has been introduced afterward to see if it can help to resolve problem with boost. The installation was already broken. Are you sure this feature break something ?
Yes. When you introduce pin_compatibility, it change the priorities and install boost and py_boost from default channel.
I know that mixing pin and classical deps (boost and pin(boost)) is dangerous. At continuum, they have a shared configuration file to be sure to have the exact same policy.
So, without this flag, it will take the boost from conda channel which is 1.66
Previously there was a bug due to the fact that the other openalea channels do not contained the latest boost version.
Cheers
Le 24/05/2018 à 14:19, Frederic Boudon a écrit :
This possibility has been introduced afterward to see if it can help to resolve problem with boost. The installation was already broken. Are you sure this feature break something ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openalea/plantgl/pull/26#issuecomment-391693322, or mute the thread https://github.com/notifications/unsubscribe-auth/ABEeSqZ_mPyn-DYbPCUSfyJsYx2jep6Qks5t1qVLgaJpZM4UL4JZ.
This broke all installation. The wrong boost package is selected and this take the lead to our channel.
We may use pin_compatible option later on, but on all packages. The current solution is to upload our packages on the same channel and give priority to the channel.