* packaging/rules/rpm/jami-all.postinst (is_distribution_supported):
Make version agnostic.
(has_rpm, is_opensuse): New procedures.
(CAN_ADD_REPO_SOURCE, JAMI_REPO, ENDTAG): Delete variable.
(jami_repo_name, jami_repo_base_url): New variables.

Change-Id: I01ee72da39a1a8377ec70ae9dc3ef218d0837633

This follows commit 2afa99fd1 in the daemon.

* build.py (run_run) <dring>: Adjust file name.
* packaging/rules/rpm/jami-daemon.spec (%install): Likewise.  Hard
code the jamid binary location as /usr/libexec/dring, to not argue
with OpenSUSE Leap's %{_libexecdir}.

Change-Id: Iea6bf3cc6c4dce853f0b7c92861dfee7b8a07bbe

Change-Id: Ie938153fd4581e6007c4c2c65b82649c56c31e4c

Change-Id: Icff500f88094c5a904095c228f68824514c157ce

AFAICT, this was made to clear some supposedly non-redistributable
files in the sources according to Debian policy.  If there's some
cleanup to do, we should do so at the level of the common source
tarball, not in a Debian-specific way.

* packaging/rules/debian/rules (override_dh_auto_configure): Remove
code repacking tarballs.
(override_dh_clean, get-orig-source): Remove.
* packaging/rules/debian/copyright (Files-Excluded): Remove.  Also
streamline the listing of copyrights to the files part of our tree,
not in bundled libraries.  Debian-specific requirements can stay in
the Debian-maintained corresponding packages.
* scripts/build-package-debian.sh: Streamline, making the release
tarball the sole input of the process.  Do not build source packages,
for simplicity (dpkg-source doesn't like our source tarball as-is).

Change-Id: I78a482ab3362e9bba8ffdc0ab60324f94715bfb8

Change-Id: I6b7f3a686b5fb74454882507e097baf96c61aeb6

as of now, the snap ecosystem only supports SPDX 2.1 identifiers.

Change-Id: Iaa35b7d47d20bd320c585a2b72fa715b9bac2a5f

Change-Id: I11d1191eedf126bfb235ab9f36216c157547f392

Change-Id: Ib2bd0ab1db50192da377b8807730ae95b0259e50

Change-Id: I4c9fc47dabaaf36d693312d98e0c0a94d031aff1

Change-Id: I661fb159a10e8c7b6e5b7261f62f91605dbe020a

Amin Bandali authored 3 years ago and Sébastien Blin committed 3 years ago

Change-Id: I33f13231006e568a8de9b0e067db4aaf6f15739c

Change-Id: If3512d8c56cb19622f72c6245f6c04c411b719e2

Change-Id: I51f28ee6e8d739ee73a775e4421e47e34aede336

Change-Id: I07cf920ed99f460bffe1d8a16f3444706f4572c3

Maxim Cournoyer authored 3 years ago and Sébastien Blin committed 3 years ago

This makes the current 'jami-all' package the one used for the
one-click install package.

* packaging/rules/debian/rules (OCI_INSTALL_DIR): New variable.
(override_dh_auto_install): Extend rule to install the files of the
jami-libqt package.  Do not include the jami-gnome in jami-all.
* packaging/rules/debian/control (jami-all): Update description.
* packaging/rules/debian-one-click-install: Delete directory.
* packaging/rules/debian-one-click-install/jami-all.postinst: Move to ...
* packaging/rules/debian/jami-all.postinst: ... here.
* scripts/make-packaging-target.py: Remove all OCI-specific targets.
* scripts/deploy-packages.sh (package_deb) [jami-all]: Do not add
package to the apt repository.
[manual-download]: Look for the jami-all package from the main
distribution directory, not in a '_oci' suffixed version.

GitLab: jami-client-qt#263
Change-Id: I4cacf26355c767d1c77b1ce478b184023481b674

Remove commented code and deprecated packages (it's bee more than a
year).

Change-Id: Ie7224c831405c07a33018ccc951a73bc05a93599

Amin Bandali authored 4 years ago and Maxim Cournoyer committed 3 years ago

Also remove unused DEBIAN_PACKAGING_OVERRIDE.

Change-Id: Ida109a811bebd1fb46fd1a8b90fb5463518382c0

Amin Bandali authored 4 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: I983607f226476c32a6862a41b55ca1b13a2c010b

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: I18c33fc508d549b8935ddf16d55556a98ad9b6d1

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: Ied0febeca35f3d39724401669427bdfecc8f093c

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

Change-Id: Ib3e5a459f907928882bd9be4427fafe75f053080

Sébastien Blin authored 3 years ago and Maxim Cournoyer committed 3 years ago

also de-duplicate code

Change-Id: I3ea9fedec5b4520e74489f3f4e03a533130d9e83

A new spec file is added, and the Fedora Docker images are augmented
with the required Qt dependencies.  The client-qt submodule is now
also included in the release tarball.

GitLab: #264
Change-Id: I2f25fdc3270a7fed13b9b0714d01feb37f270077

Tackle the growing complexity of the packaging by splitting the
problem into smaller parts.  This change makes the daemon its own
package, along the client library and the GNOME client.

The build script is updated to reflect these changes, and
unused/obsolete spec files are removed from the project.

GitLab: #264
Change-Id: I5813e48e0c1248875a7a8f0ee1ec6fb2b87faef4

GitLab: jami-packaging#91
Change-Id: I491c53dc7647820b0df6aa8a66ee38b37dc8bddb

Change-Id: Ic801a5c9fa5ad78882fb7baab7b943d1fcf06a44

Change-Id: Id24a6a8b2db26842a16e9ad4bbdbb0c30447bb96

Change-Id: I0636da7d2b26eb75a6f8f3a37a2c92f1fd05fdfd

Change-Id: I8bbb844c44a21b24574ca59b59dffd7c97f640de

Sébastien Blin authored 4 years ago and Maxim Cournoyer committed 4 years ago

For apt-based systems, a 'ring' distribution is kept along the new
'jami' one to keep supporting existing users until April 2024.

GitLab: jami-packaging#3
Change-Id: Ie589175e6abff8e4b1b252dff7eade4729d46a62

Debian 9 packaging is removed as well, not because it is EOL, but
because it doesn't have the runtime required to run Jami (the daemon
requires C++17 but GCC 6 in Debian stretch doesn't support it).

A 'list-package-targets' Make target is also added; it'll be used by
the CI.

Change-Id: I87a26b14ea48bd17ebccb536f23a5f2637f28743

Change-Id: Ibfe20a56db762a844ed458d4bea1331051e0f0b5

Restore required packages, and also add missing -DENABLE_STATIC=true
for client-qt.

Change-Id: I49997afa01109e1326ec06f06051504311f8471f

Adapt the main jami snapcraft.yaml file for client-qt, and move a copy
of the previous client-gnome snap to a new jami-gnome/ subdir.

Change-Id: If1e014c7af9d89c1fe3d13b5d365d74c0ecf368d

Change-Id: I9df8043ec2da9c2a0c4ba3a2e09e5feadb71e585

Without libssl-dev available in build time, we would fall back on
building our own from a locally-built libressl, which would have
incorrect paths for location of certificates: the resulting snap
would incorrectly try to look for certificates under
parts/jami/build/daemon/contrib/x86_64-linux-gnu/etc/ssl, which is
not available after build, instead of a more sensible /etc/ssl.

Change-Id: I76cb847d18561e29250d4b9d39d1993dabc9a864

Amin Bandali authored 4 years ago and Sébastien Blin committed 4 years ago

Change-Id: I309f31ba1d23a9cbc48e2936b7591ae4fba40a76

Change-Id: I9e8e666f09949d56c3c14c43b834f1d39c10c9db

Change-Id: I5b24b809cec3763c44808fe9f056cba862336531