Release as Debian Package

Roger Lipscombe roger@REDACTED
Fri Mar 18 10:00:53 CET 2022

+1 to Hugo's point: We used 'fpm' for building our
internally-distributed .deb files; then we used apt-s3 (or whatever
it's called) to, well, pull the .deb files from an S3 bucket. Prior to
that, we used the full debbuild toolchain, but it was overkill for
internal releases. For simpler .deb files, we just built them with a
shell script and 'ar', etc.

otoh, if I were to do it again, I'd go all-in on containers.

On Thu, 17 Mar 2022 at 22:55, Hugo Mills <hugo@REDACTED> wrote:
> On Thu, Mar 17, 2022 at 04:29:06PM -0600, Joseph Lloyd wrote:
> > My team has written our first Erlang program.  Now, we are preparing for
> > deployment.  I can see how to use rebar3 to create a .tar file, but are
> > there tools or workflows out there that can help us easily create a .deb
> > file instead?
>    FPM ("Effing Package Management")[1] does the absolute minimum job
> for building packages (in multiple formats -- .deb is one). It's not
> pretty, and I suspect the resulting packages will never be accepted
> into an upstream distribution, but if you're deploying internally
> only, it should do the job nicely.
>    If you're building for external consumption, then you should
> probably learn to do the packaging properly. I can't help there, I'm
> afraid.
>    Hugo.
> [1]
> --
> Hugo Mills             | "Your problem is that you have a negative
> hugo@REDACTED | personality."
>  | "No, I don't!"
> PGP: E2AB1DE4          |                              Londo and Vir, Babylon 5

More information about the erlang-questions mailing list