signal-cli is a command-line interface for libsignal-service-java. It supports
registering, verifying, sending and receiving messages. To be able to link to
an existing Signal-Android/signal-cli instance, signal-cli uses a patched
libsignal-service-java, because libsignal-service-java does not yet support
provisioning as a slave device. For registering you need a phone number where
you can receive SMS or incoming calls. signal-cli is primarily intended to be
used on servers to notify admins of important events. For this use-case, it has
a dbus interface, that can be used to send messages from any programming
language that has dbus bindings.
===> The following configuration options are available for signal-cli-0.14.8,1:
DBUS=on: D-Bus IPC system support
===> Use 'make config' to modify these settings
Mk/**java.mk: Convert bsd.java.mk to USES
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net-im/signal-cli: Return to the pool
It would be great to update this port to the newest version available
upstream. Unfortunately, I couldn't get the newer versions to work
reliably on FreeBSD.
net-im/signal-cli: Fix service signal_cli runcli
runcli_precmd got committed by mistake.
PR: 261754
Reported by: mikael
Fixes: 1d21db50cb05 net-im/signal-cli: Include patches bringing B-Bus support
MFH: 2022Q1
net-im/signal-cli: Revert update to 0.9.1
signal-cli stopped working with this update. Let's roll back.
This reverts commit 04497570c3e86c251353a323b64bed6523e5dd27.
Update to 0.8.1
- Switch to depending on upstream tarballs for all the JAR files this port
needs. Since 0.8.0, the upstream switched to a Kotlin-based Gradle file,
which broke the Gradle dependency resolution mechanism implemented in
files/build.gradle.in. It is unproductive to fix that script. Let's just
use the provided JAR files.
- Java is no longer used to during build, so set JAVA_RUN=jre.
- Release notes:
https://github.com/AsamK/signal-cli/blob/v0.8.1/CHANGELOG.md
Mark as broken on FreeBSD 11.4 amd64
It is unclear to me why it happens only on this specific FreeBSD version.
Exception is:
org.gradle.launcher.daemon.client.DaemonDisappearedException: Gradle build
daemon disappeared unexpectedly (it may have been killed or may have crashed)
Reported by: pkg-fallout
net-im/signal-cli: Update to 0.6.10
Release notes:
- https://github.com/AsamK/signal-cli/releases/tag/v0.6.9
- https://github.com/AsamK/signal-cli/releases/tag/v0.6.10
Port changes:
- Improve the comment about jffi-native to be a bit more clear.
- Set JAVA_HOME for Gradle explicitly. Gradle was not picking up the right
Java version automatically.
- Remove post-patch; it is no longer needed.
- Bump the required Java version to 11+ as documented by the upstream.
net-im/signal-cli: Include patches bringing B-Bus support
This commit updates dbus-java and its dependencies to 3.2.2, which includes
patches contributed by grembo@, which make signal-cli work nicely with
D-Bus on FreeBSD. It is a great thing because now it is possible to use
various TUI clients for Signal.
Additionally, we include an rc(8) service now, which allows users to run
signal-cli as a system service if they desire to use D-Bus system bus to
talk to signal-cli.
Other changes:
- Make _get-links depend on patch instead of extract (sometimes we need to
patch Gradle config files to get the versions we really want).
- Introduce ORIGINAL_BUILD_GRADLE variable for robustness.
- Put some documentation into pkg-message to help users start using
signal-cli.
- Set JAVA_HOME in the signal-cli script; it is a bug fix.
Special thanks to: grembo@
Update to 0.6.8
- Set LICENSE_FILE.
- Drop LIB_DEPENDS, libunix-java.so is no longer needed.
- Use ${GMAKE} to call Gmake.
- Bump JAVA_VERSION to 8+
- Update build.gradle.in to make it compatible with the recent Gradle
versions.
- Drop unnecessary JAVA_OPTS from signal-cli.in.
Release notes:
https://github.com/AsamK/signal-cli/releases/tag/v0.6.8
Chase devel/libmatthew plist changes
Also:
- Bring back vendored libmatthew JARs. It turns out that the build script
is not picking up the ports version of libmatthew when generating the
signal-cli script (share/signal-cli/bin/signal-cli). Use the vendored
version for now.
- Remove an unnecessary comment.
New port: Command-line and D-Bus interface for Signal and libsignal-service-java
signal-cli is a command-line interface for libsignal-service-java. It
supports registering, verifying, sending and receiving messages. To be able
to link to an existing Signal-Android/signal-cli instance, signal-cli uses
a patched libsignal-service-java, because libsignal-service-java does not
yet support provisioning as a slave device. For registering you need a
phone number where you can receive SMS or incoming calls. signal-cli is
primarily intended to be used on servers to notify admins of important
events. For this use-case, it has a dbus interface, that can be used to
send messages from any programming language that has dbus bindings.
WWW: https://github.com/AsamK/signal-cli
