Change-Id: I4e08d256c651cdbc143c8315329931c6d95364c7

Change-Id: I54ef1d4adc7823fe3a38cd9ff7e7ee9af6a774bb

The deb-pack targets build a Guix pack of the jami-qt client in the
.deb format, ready to be installed on any dpkg-based GNU/Linux
distribution.

* Makefile (RELEASE_VERSION, RELEASE_TARBALL_FILENAME): Export
variables.
(has-guix-p): New target, to be used as a predicate.
(portable-release-tarball): Rewrite in terms of the above.
(SUPPORTED_GNU_ARCHS, DEB_PACKS, DEB_PACK_TARGETS): New variables.
(guix-pack-command, define-deb-pack-rule): Likewise.
(deb-pack-x86_64, deb-pack-i686): New targets.
(PACKAGE-TARGETS): Register them.
* guix/guix-pack-manifest.scm: New file.
* guix/guix-pack-deb.postinst: Likewise.
* guix/manifest.scm: Specify qtbase to be at version 5, as Guix now
has version 6 too.
* packaging/rules/debian/jami-all.postinst: Harmonize.
* scripts/deploy-packages.sh (package): Simplify and register the
'guix-deb-pack' distribution.
* Jenkinsfile (Sign & deploy packages): Simplify to deploy all the
packages subdirectories.  This makes it easier to handle multi-arch
packages for the same distribution, and removes the need to encode the
distribution information in the target name.

Change-Id: Id6f69e7a5872a39b4b8f50fa09c8ec3475e9c896

https://review.jami.net/c/jami-client-qt/+/19283 recently marked
Python 3 as a required build depdendency for building client-qt,
as it's needeed for generating 'resources.qrc' in build time.

Change-Id: Ib7eb3822ec5af5e4223d8a05b52d7cb5bb22e8d5

Change-Id: I195452f1b14a835d08b4e1be734b7a9bd880ef8a

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

* packaging/rules/debian/rules (override_dh_auto_configure): Move
recipes to ...
(override_dh_auto_configure_build): ... here.  This is necessary as
the LRC now must find the share library of the daemon, hence it must
be built before the LRC configuration occurs.
<-DENABLE_LIBWRAP=true>: New option when configuring the LRC.
* packaging/rules/rpm/jami-libclient.spec (%build): Likewise.
* scripts/install.sh (lrc_cmake_flags): Likewise.
(OSTYPE): Remove variable.
(sharedLib): Remove variable.  The Jami daemon shared library is
needed when dynamically linking against it when libwrap is enabled.
* packaging/rules/rpm/jami-daemon.spec (%build): Drop the --disable-shared
option.
(%files): Register the libring.so dynamic library.
* packaging/rules/debian/rules (override_dh_auto_configure): Drop the
--disable-shared option.

GitLab: jami-packaging#101
Change-Id: Id1acaaf15a0f3d561c73bf34dde48f4eaf058eed

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

This reverts commit 62f547b5.  The fix
now more properly lives in the contrib build system.

Change-Id: I7bb7d1f302c91be46627fc26eddece1d768fb308

Change-Id: Icc26fef916e323d87247abac8d45f7e55bc100e8

* packaging/rules/rpm/jami-daemon.spec (%files): Remove jami_contact.h header.

Change-Id: If13ca9d29a4bd65066857a9bce7e3b44379515cb

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

* packaging/rules/debian/rules (override_dh_auto_build): Invoke the
contrib build system with GTKDOCIZE set to false to workaround
https://savannah.gnu.org/support/?110503 present in Debian unstable.

Change-Id: I03e6d070d33fb126e3777517b6b4f1b4f042e315

* packaging/rules/debian/rules (LDFLAGS): Filter out the
-Bsymbolic-functions linker option added by default on Ubuntu.
[ubuntu_21.04]: Do not force the bundling of FFmpeg.

Change-Id: Ia83c305808072a4e5923530421924eb85f9b5b5e

Change-Id: I9ed56eee9cc52a6423af3daafa3b57b494481e03

Change-Id: I4a03364f4062379fe8dc849ba02343d14de730f9

This give us more controls about bugs and anyway, we're going to
use Qt 6.2 for macOS support.

Change-Id: I78c17a9984248b4dad08ab2091532159335d4c97

Change-Id: I10a69b2026f6e6aa963ffaa95702c0c58c39d216

Change-Id: I8e6f99f0322d8787c8991228bdd6681b950b6a19

Automated via: $ git grep -l dring | xargs sed -i 's/dring/jamid/g'

Change-Id: I67715a37e0fae42a0e4d9ce42bd01becc1ac77f5

This is a follow up to the f0fb8148ba7f453d73e31e1cece2dcffae68e878
commit (Use the PROGSHAREDIR macro to refer to the custom datadir) in
the daemon, that moved the ringtones from a hard-coded location of
/usr/share/ring/ringtones to $datadir/jami/ringtones.

* packaging/rules/rpm/jami-daemon.spec (%files): Adjust accordingly.
* scripts/install.sh (client_cmake_flags) <DRINGTONE_DIR>: Likewise.

Change-Id: Ia9d3403f5600a4ab4eefe28ee20611afc3f5e8b0

* build.py (run_run) <dring>: Adjust file name.
* packaging/rules/rpm/jami-daemon.spec (%install): Likewise.

Change-Id: Iedc4e0803bda19d139b29a4ccc669dcc8cc3fb9f

This change normalizes the hanging indent to 2 spaces.

Change-Id: I98bd6919eae547b946af2c59a14cbee96ee50a9d

Workaround <https://bugreports.qt.io/browse/QTBUG-94800>.

This is to avoid out of memory conditions during the build, which
requires up to about 2 GiB of memory per parallel process.  There was
also a problem with how the MAKEFLAGS was passed, which led
qtwebengine to be built using all the CPU cores even when specifying a
lesser NO_CPUS value.

* packaging/rules/debian-qt/rules (min, max): New functions.
(NO_CPUS): Express in terms of max.
(AVAILABLE_MEMORY, MEMORY_REQUIRED_PER_CORE, COMPUTED_JOB_COUNT)
(JOB_COUNT, MAX_PARALLEL_BUILDS): New variables.
(override_dh_auto_build): Override to manually control job count.
Specify NINJAFLAGS for the Chromium build.
* packaging/rules/rpm/jami-libqt.spec (min, max, cpu_count)
(available_memory, computed_job_count, job_count): New macros.
(%build): Re-indent and use the above 'job_count' variable as
the number of parallel jobs.
(%install): Likewise.

Change-Id: I9134c1e63e92104a1da8435670e2919ce692040c

Change-Id: Ib5ad6c091560f7fc4ee9734ca283e78c90d9d769

* 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