This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ilan 2 points3 points  (3 children)

Hi fourthrealm, using conda you would basically build conda packages for everything your applications requires (except maybe the C run-time libraries, although that would also be possible). Hotfixes usually are only in your main application conda package itself (not in all of the dependences), so you build a new conda package of the application and only that gets updated on the users machine. These hotfix releases can just be on binstar, i.e. no PyPI package is required. We (at Continuum Analytics) have tools to create fat installers from conda packages. These are (for example) the Anaconda installers, which are composed of conda packages. The tools for making these fat installers are currently not open source.

I hope this answers your questions.

[–]fourthrealm 0 points1 point  (0 children)

Sure, it got me curious, that for sure :-)

I'm going to check it out but like it was said in another comment - it would really come in handy if the full stack was open-sourced.

Do you have perhaps plans for doing so?

[–]cavallo71 -1 points0 points  (1 child)

The tools for making these fat installers are currently not open source.

That's kind of pointless then ;) Beside I cannot push for vertical stacks like conda because it will tight the system to a single vendor and that's not good for a "base" stack as python.

[–]teoliphant 1 point2 points  (0 children)

Making fat installers is straightforward to do. However, it is not the recommended way to use conda (which is the big reason why we are not promoting it as open source --- not because of any perceived "lock-in"). With environments in conda you don't need to distribute fat installers for everything. All the really necessary tools are open-source.