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

The recently introduced 'guix shell' command automatically manages a
cached profile for us; prefer it to 'guix environment', and do away
with a channels file, given fixes in Guix have now been incorporated
in the main branch.

* Makefile (portable-release-tarball)<guix environment>: Replace by
'guix shell'.
* build.py (run_dependencies)[guix]: Likewise, and do not use a
channels.scm file.
(run_install): Likewise, and provide a hint when TARBALLS is not set.
* guix/channels.scm: Delete file.
* guix/manifest.scm: Adjust comment.

Change-Id: I50ca99e51f0ebca136c9bbc5a0ca3063075432b4

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

Change-Id: Id592bc760b5ae10f74ed13c47ba7602f633d80e3

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

Change-Id: I99a20bcf357032a6fcf689265c93670dcf65b8b7

Change-Id: I98725b2669b357fb86dc653cb7d7ead6f34cb355

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

This enables building Jami in a development setting on any GNU/Linux
distribution, provided Guix is installed.  It supports building both
the Qt and the GNOME clients.  It uses ffmpeg and pjproject from the
contribs.

Change-Id: I1bf0c9f3f9c08361b9016fe04581902ec27f2312

The phony tarball-producing targets will now always clear the
tarballs.manifest file before generating a new release tarball,
ensuring it doesn't contain stale information.

A new 'portable-release-tarball' target is also added to offer an easy
to use target that was previously implemented ad-hoc in the CI.  Move
this logic here as a portable release tarball is useful for packagers
wanting to test locally with the various supported platforms.  The
Jenkinsfile now makes use of it.

* Makefile (daemon/contrib/native/Makefile): New target.
(tarballs.manifest): Add the above target as a prerequisite and remove
invocation to bootstrap script.  Invoke make with --no-print-directory
to prevent entering/leaving directory messages from appearing in the
output (it's supposed to be on when using --silent, but when the make
invocation is nested, it doesn't seem to be the case).
(release-tarball): Also clear the tarballs.manifest when invoked.
(purge-release-tarballs, portable-release-tarball): New targets.
* guix/minimal-manifest.scm: New file.
* Jenkinsfile ('Generate release tarball): Use it to spawn the
container used to build the release tarball.  Also expose /usr/bin/env
in the container.  Use the new 'portable-release-tarball' target to
simplify things.  Fix the shebang line; it needs to be the first line
of the script.

GitLab: jami-packaging#98
Change-Id: I3b55e25933108ae9930bc9fcc867f9fa51d796f2