[onli]

Yeah, sure. Because it is so easy to build packages, as the shortlyness of the article and the amount of the involved commands prove, it is surely a fast and good way to produce those packages to deploy your code.

For reference, it is not. Packages solve a different problem, and he even writes it: Well made packages with dependencies enable everyone to use the software, regardless of the involved system, given some constraints. They don't need to be fast and they don't need to be easy (as much as I would like them to), because they are used by specialists in a lengthy process.

But if one deploys code on a system, we know a bit more of the system than "it is a computer". Maybe it is a standardized production instance, maybe it is a vm - in any case, we have direct access. So it is possible to use easier and faster methods to deploy code directly, without having to resort to arcane voodoo.

If you really want to use debs for deployment, at least use checkinstall and handle the dependencies manually. Then you need at most 3 command (./configure, make, checkinstall).