{"action":"created","issue":{"url":"https://api.github.com/repos/conda-forge/conda-forge.github.io/issues/23","repository_url":"https://api.github.com/repos/conda-forge/conda-forge.github.io","labels_url":"https://api.github.com/repos/conda-forge/conda-forge.github.io/issues/23/labels{/name}","comments_url":"https://api.github.com/repos/conda-forge/conda-forge.github.io/issues/23/comments","events_url":"https://api.github.com/repos/conda-forge/conda-forge.github.io/issues/23/events","html_url":"https://github.com/conda-forge/conda-forge.github.io/issues/23","id":132803016,"number":23,"title":"Dependencies on  libraries","user":{"login":"ChrisBarker-NOAA","id":916576,"avatar_url":"https://avatars.githubusercontent.com/u/916576?v=3","gravatar_id":"","url":"https://api.github.com/users/ChrisBarker-NOAA","html_url":"https://github.com/ChrisBarker-NOAA","followers_url":"https://api.github.com/users/ChrisBarker-NOAA/followers","following_url":"https://api.github.com/users/ChrisBarker-NOAA/following{/other_user}","gists_url":"https://api.github.com/users/ChrisBarker-NOAA/gists{/gist_id}","starred_url":"https://api.github.com/users/ChrisBarker-NOAA/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ChrisBarker-NOAA/subscriptions","organizations_url":"https://api.github.com/users/ChrisBarker-NOAA/orgs","repos_url":"https://api.github.com/users/ChrisBarker-NOAA/repos","events_url":"https://api.github.com/users/ChrisBarker-NOAA/events{/privacy}","received_events_url":"https://api.github.com/users/ChrisBarker-NOAA/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-02-10T20:05:21Z","updated_at":"2016-03-09T15:25:44Z","closed_at":null,"body":"What should the policies be about dependencies on libs?\r\n\r\nKey question: what system libs can be depended on.\r\n\r\nSecondary question -- what should be done with libs needed:\r\n  - statically link ?\r\n  - ship dll, so, etc with package\r\n  - provide separate packge for lib (dll, so, etc.)\r\n\r\n@JanSchulz wrote (in issue #16 ) (with my comments):\r\n> IMO: Linux: xserver but nothing else?\r\n\r\nPlus the core libc of course -- essentially what Anaconda is built on .\r\n\r\n> Windows: no extra installed packages but the MS compilers, e.g. repackage r-tools and libswhich are > needed (tk, ...). No special libpath locations (old mpl recipe in conda-recipes), \r\n\r\n+1\r\n\r\n> no extra installations of dependencies (e.g. python-igraph needs igraph (c lib) as dependency).\r\n\r\nI don't get this -- did python-igraph require that you separately install igraph?\r\n\r\n > This would mean that we have to put c libs into the same conda channel as the python libs.\r\n\r\nYes -- that is definitely what should be done. If you are packaging a python wrapper around alib, the lib itself should be provided as a conda package.\r\n\r\n> Also interesting: what to compile in as a static dependency: I have the feeling that on windows pretty \r\n> much everything is included in the final package and not used via a dll file...\r\n\r\nyeah, it's looking that way -- I assumed that part of the POINT of conda was to be abel to provide libs that various packages could use. But I've been wrestling with this -- having to hack in a change to the PATH environment variable at run time -- ugly! But conda may have fixed this -- I think the LIbrary dir is now added to path in miniconda/anaconda -- but I haven't tested yet.\r\n\r\nBut if it can work, I think we should prefer that libs are installed as dlls by a separate package -- that way they can be used by multiple other packages. But statically link if it really is a only for this package lib.\r\n\r\n\r\n\r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/conda-forge/conda-forge.github.io/issues/comments/194344327","html_url":"https://github.com/conda-forge/conda-forge.github.io/issues/23#issuecomment-194344327","issue_url":"https://api.github.com/repos/conda-forge/conda-forge.github.io/issues/23","id":194344327,"user":{"login":"jjhelmus","id":1050278,"avatar_url":"https://avatars.githubusercontent.com/u/1050278?v=3","gravatar_id":"","url":"https://api.github.com/users/jjhelmus","html_url":"https://github.com/jjhelmus","followers_url":"https://api.github.com/users/jjhelmus/followers","following_url":"https://api.github.com/users/jjhelmus/following{/other_user}","gists_url":"https://api.github.com/users/jjhelmus/gists{/gist_id}","starred_url":"https://api.github.com/users/jjhelmus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jjhelmus/subscriptions","organizations_url":"https://api.github.com/users/jjhelmus/orgs","repos_url":"https://api.github.com/users/jjhelmus/repos","events_url":"https://api.github.com/users/jjhelmus/events{/privacy}","received_events_url":"https://api.github.com/users/jjhelmus/received_events","type":"User","site_admin":false},"created_at":"2016-03-09T15:25:44Z","updated_at":"2016-03-09T15:25:44Z","body":"My docker is a bit weak (I am a big vagrant users) but I have been looking for a reason to learn more.  I'd be happy to maintain a manylinux like Docker image for conda-forge.\r\n\r\n I've been playing with the manylinux Docker image this week and it really a great tool.  I'll try to build a version similar for the project and submit a PR against conda-smithy."}}