rtpengine

1.5 GiB

Tree: 9e2bf2bbda

Author	SHA1	Message	Date
Victor Seva	6e7aab6f70	TT#124273 pkg: use backports scripts to generate different flavours * pkg/deb/debian should be the only source * pkg/deb/debian/backports: scripts to generate differences This way is quite easy to maintain different versions, the differences are managed via scripts Change-Id: I0ac3a35fe3facf005564141563e2fb11b73cbefc	4 years ago
Richard Fuchs	bbfe168b72	TT#124273 add non-NGCP Debian packaging For this initial version, these are mostly copies of the existing /debian tree, with `ngcp-rtpengine` renamed to `rtpengine`, added "conflicts" with the `ngcp-rtpengine` packages, and NGCP-specific "suggests" removed. Change-Id: I64289f9907ec09d003a96b8ac81f83c79d413747	4 years ago
Guillem Jover	0224a49162	TT#40459 Move the rtpengine NFS mount point into its own systemd unit We do not use a proper mount unit because that requires the mount point to be encoded in the filename which is variable and depends on the value coming from config.yml. Change-Id: Ibb637c533c94bc3db119111460ca647a50a205af	8 years ago
Guillem Jover	79807a9c2e	TT#26264 Use better systemd native units While still not the ideal implementation, this is certainly better than the sysvinit script wrapper. We then will "only" need to move the setup scripts into proper service files later on. Change-Id: I990d6847117a4b91a8365a5e307fd96cf5b1899f	8 years ago