apt-get

When OpenSSL has a vulnerability, they announce it after the fix is out, distro maintainers release updated packages, I run `apt-get update && apt-get upgrade` or equivalent.

If installing via apt-get, that means creating a debian package that provides lxc-docker-1.6.2 (docker 1.7 broke backwards compatibility in output of docker ps).

> Trouble starts the minute you start relying on commands like this: sudo apt-get install mypkg So what's wrong with `sudo apt-get install mypkg=<version>`?

So then if you want the newer version you can do apt-get install <package>/<release>.

There's no need to wait: the n900 was real Linux (with X, apt-get and anything you could want) as was the n9.

Must be cumbersome, there's no equivalent of Gemfile.lock and bundler for apt-get, is there?

Look at firefox as your apt-get and the H264 plugin as something that you can either download a compiled binary of or compile yourself.

Just one non trivial example: I can secure Ubuntu against sshd attacks pretty good and easy with `sudo apt-get install fail2ban`.

Check the build-depends in debian/control or try apt-get build-dep erlang first.

An apt-get and your updates are handled nicely for you.

Looking forward to the day I can apt-get this in Debian and Ubuntu!

Of course once I know that I need to perform an update, it doesn't matter if I run `apt-get upgrade` or `go build foo`.

So my team doesn't have to run "apt-get install postgresql" on their dev machines?

It is not just "use unstable", it is "use unstable if you want to apt-get install stuff".

That's what "apt-get autoremove" is for.

Ultimately I thought this graph to support the introduction of build profiles into Debian (now so happened with the Jessie release) as well as to promote that a tool like "botch" (you can `apt-get install` it) is necessary to automatically make this graph acyclic for you instead of doing this through year long manual work.