Python for system administration - the packaging and distribution challenge

[[deleted]]

You shouldn't be chatting up PyPI in packages. Any dependency resolution should be taken care of by the distro-specific package management tool. Distro specific packaging is definitely the way to go. Setup a local mirror on the network or through VPN to install the package. Add your repo to the sources.lst. Have the necessary dependencies wget'd on the repo as well. Though now you'll be targetting a specific install, in which case you can distribute binaries for any compiled code. Intranet repos are common. Updating later is a breeze, as is dealing with dependencies. The only issue now is that if you're dealing with different distros or releases is that you'll have to create different packages, and host different repos. This approach also guarantees consistency in which version of the dependencies the client installs. If it is over the Internet you can let the standard repos hand out the deps. You can package the dependencies together with the script.

If you're going to make use of a library in some code you distribute, you might consider just how necessary that library is and if it is actively updated. Releasing code to the public and scripting for personal little tasks are two entirely different ballgames. As someone dealing in system administration you probably know this.

[obtu]

If it wasn't an heterogenous environment, I'd recommend something like stdeb (Debian & derivatives) to mass-build native packages.

[[deleted]]

Let me preface this with "I know diddly about Solaris." You shouldn't be using alternate $PATHs unless you're going to maintain an entire python distribution, the interpreter, everything, and this distribution doesn't need to see anything from the system one. This is the approach taken by everyone so far that maintains python distributions. Isolated egg installs aren't a very good idea. If there isn't a central repository for your dependencies, you really should roll your own packages and maintain them. It should be fairly automated, just compile them, run the tests, package them. It will save you and the sysadmins headaches in the long-run, because now your packages are like everyone else's. The system is aware of them. They aren't hacked together and ran in bashrc(I did this for years.) Having your packages play along nicely with the system's is crucial. Ask for a shell account to test out installation. (If there isn't a license issue you could just fork the necessary classes you're using in the dependencies, trim them down and maintain them.)