Commit Graph

9 Commits

Author SHA1 Message Date
Oliver Smith ed3991574a Bump version: 0.2.0
Change-Id: I3a175b0c7585268d748b007ab89110987b7e04cf
2023-10-31 13:00:53 +01:00
Oliver Smith 3c8e580ce6 debian/rules: extract build_dep.tar.gz first
Currently dh_auto_build is a no-op, but move extracting depends up in
case we add a Makefile here too.

Related: osmo-epdg I2bb0b5f608cd5d9a24c2a367425c524447bd002c
Change-Id: Ib64671a8b4629dde1e21b18a6405f7ae7d87a46f
2023-10-06 14:30:40 +02:00
Oliver Smith 2f173b712e debian: set compat level to 10
Related: OS#5958
Change-Id: I49fcc4fe9d3e795f8c3514d35ff3e2beca2917d1
2023-04-25 16:48:34 +02:00
Daniel Willmann 742f8d5b0f Release new version: 0.1.2
Fixes: OS#5646
Change-Id: I2b71212009149ea46effecb08d96620cc67c944b
2022-08-19 17:45:45 +02:00
Oliver Smith 6e28afb504 Bump version: 0.1.1
Change-Id: I30c104822a96d14f80cad320b801149f38b886b7
2022-07-22 12:52:24 +02:00
Alexander Couzens c243463bf7 debian: add generate_build_dep.sh to vendor erlang dependencies
To build on OBS the source package must include all dependencies.
Downloading dependencies isn't allowed. generate_build_dep.sh will
download all dependencies.
The jenkins job to update OBS should do this before calling
`dpkg-buildpackage -S` to build a source package.

Related: SYS#6006
Change-Id: I22041887fd1b72ea328605d18801d412b86bfc9c
2022-07-20 19:51:00 +00:00
Alexander Couzens 700979a5b1 debian: rework packaging
- use the rebar3' debian/rules as template
- use override targets instead of the exact targets
- only install the escriptize osmo_dia2gsup file

Related: SYS#6006
Change-Id: I40add168875de87ef0cc62deeb5377d2ce080e45
2022-07-20 19:51:00 +00:00
Alexander Couzens a9faa72537 debian: add missing Build-Depends debhelper
Related: SYS#6006
Change-Id: I1b5774983d705c54c909823da329068a7aa0a9a8
2022-07-20 19:51:00 +00:00
Oliver Smith 173095f9fa debian: add packaging
Add initial debian packaging and a systemd service that starts
osmo_dia2gsup. Given that dependencies listed in rebar.lock are not
packaged in debian 11, this just uses rebar3 to download and compile
the dependencies during the build.

Resulting erlang files are installed to the following path, where they
become available in the erlang shell (erl):
  /lib/erlang/lib/{name_of_component}/ebin/

Related: SYS#6006
Change-Id: Ic55bca1260f992d0ed8583e7c7fe948ba0160d4d
2022-07-15 15:08:51 +02:00