Packaging and Deploying Continuum Analytics' Anaconda with Munki

[Luke Tinker]

Hi Munki Community,

Just thought id post on here about packaging Anaconda,

In my particular case i'll be talking about Anaconda with Python3 bundled in it,

since this discussion is something others might have use of.

So i need to package Anaconda in my environment,

it is software that is actually designed to be installed in the Users home directory,

I am not particularly sure how you could ever do this with Munki so i am open to anyone who has an idea adding to this post.

With my environments the user accounts are transient so this would never be useful anyways,

so my opted plan is Install Anaconda to '/usr/local/anaconda3' which will be owned by root:wheel with the unix permissions being 755,

effectively a read/execute only install to the end users.

now for the actual packages provided by Continuum they provide 2 methods,

a .pkg file and a shell script which includes the binaries in the script.

It would be easy to make the bash script they provide install to /usr/local/anaconda3 with munki,

however this would mean its effectively a nopkg install which would need a few extra scripts,

as well as the nopkg approach with munki not accepting parameters means the script would need to be modified which makes room for error.

so the other option would be to do something similar to the one for Office 2016 at https://derflounder.wordpress.com/2015/08/05/creating-an-office-2016-15-12-3-installer/

where the installations wrapped in another package which uses inclusive scripts to do the install which would pass the necessary parameters.

I'd Love to head from anyone as to their opinion on these approaches or if they have any other ideas as to how to approach the situation.

I'll end up posting the directions i have taken and any scripts used to complete the install/uninstall with Munki.

Cheers,

Luke

[Luke Tinker]

No Hits?

well this is what i have planed on going with,

I have pkg'd their command line installer which is a batch script with the binaries embedded into a pkg built in iceberg,

i then have a bash as a post install script in the pkg 

it can be found at https://gist.github.com/ltinker/316001a13d93a2f823dac267f999dd03

the publishers bash script is simply added to the additional resources section of the pkg.

next up, in munki the pkg is being uninstalled via a uninstall_script embedded in the pkginfo plist.

which can be found at https://gist.github.com/ltinker/4194eb77ac90ef645c8d2e4ef4d960b2

It may seem pretty simple,

but i am trying to figure out a good universal structure for packaging things like this so that later i can move onto separating it so it can be autopkg'd.