The sources previously hard-coded the location of the default Jami
ringtone as "/usr/share/ring/ringtones/default.opus". It should
instead be computed from the already existing PROGSHAREDIR macro,
which is built from Autoconf's configurable datadir.
* globals.mk (-DPROGSHAREDIR): Rename the 'ring' subdirectory to
'jami'.
* meson.build (conf): Likewise.
* ringtones/Makefile.am (dist_jamiringtones_DATA): s/ring/jami/g
* ringtones/meson.build: Likewise.
* src/account.cpp (DEFAULT_RINGTONE_PATH): Define in terms of
PROGSHAREDIR.
* bin/dbus/Makefile.am (libclient_dbus_la_CXXFLAGS): Remove extraneous
flags, already propagated via AM_CPPFLAGS. Honor AM_CXXFLAGS.
* src/client/Makefile.am (libclient_la_CXXFLAGS): Remove.
* src/plugin/Makefile.am (libplugin_la_CXXFLAGS): Likewise.
Change-Id: Icaa0a92e896f86b0bb07f82e4079570db08fafbd
This change renames the dring binary to jamid on GNU/Linux, and from
ringcli to jamid on the other Windows/Mac platforms.
* .gitignore: Ignore bin/jamid instead of bin/dring.
* bin/Makefile.am (bin_PROGRAMS)[HAVE_WIN32]: Replace ringcli by
jamid.
(ringcli_SOURCES)[HAVE_WIN32]: Rename to jamid_SOURCES.
(ringcli_CXXFLAGS)[HAVE_WIN32]: Rename to jamid_CXXFLAGS.
(ringcli_LDADD)[HAVE_WIN32]: Rename to jamid_LDADD.
[HAVE_OXS]: Likewise for each of the above 4 variables.
(bin_PROGRAMS): Replace dring by jamid.
(dring_SOURCES, dring_CXXFLAGS, dring_LDADD): Replace the 'dring'
Automake variables prefix by 'jamid'.
* bin/dbus/cx.ring.Ring.service.in (Exec)<dring>: Rename to 'jamid'.
Change-Id: I3f41846a38e74e2f3c6f687a46e1a208f0083ca2
with lasts ms patches, audio only participants dummy video was not being attached to conference mixer, causing participant to not show
Change-Id: I4621562e901aec7dfed6c6ae4a543724f9ccb0d3
GitLab: #565
Executables are typically installed under bin/, sbin/ or libexec,
rather than lib/. The problem was noticed when trying to use Jami
with a Guix relocatable pack, which only wraps executables found under
the above locations. Since dring is a daemon and should not be run
directly by users under normal circumstances, the convention is to use
the libexec directory, according to the File Hierchy Standard 3.0.
Also tackled in this change is the substitution of the Autoconf
variables at installation time rather than configuration time, as per
the GNU Coding Standards. The following solution is taken from
https://github.com/gentoo/eudev/pull/183/commits, which in turn is
adapted from the Autoconf manual (c.f.: info "(autoconf)Installation
Directory Variables").
* bin/Makefile.am (ringlibdir): Delete variable.
* bin/dbus/Makefile.am (do_subst): New variable.
(cx.ring.Ring.service): Derive from the cx.ring.Ring.service.in
template.
[HAVE_WIN32]: (ringlib_PROGRAMS): Rename to ...
(bin_PROGRAMS): ... this.
[HAVE_OSX, RING_DBUS]: Likewise.
* bin/dbus/cx.ring.Ring.service.in (Exec): Adust.
* globals.mk (ringlibdir): Delete variable.
* configure.ac [with_dbus] <AC_CONFIG_FILES>: Remove
bin/dbus/cx.ring.Ring.service. Also remove the LIBDIR variable, no
longer used. Fix indentation.
Thanks to Vladimir Stoiakin for providing feedback on this change.
Change-Id: I845bf2bd590a9457e70ca173027217b8f164d713
Incoming transfers should be preserved in the conversation's data
directory by default. This will prevent broken pending file
transfers and chat UI when the user cleans their download folders.
Subsequent commits to the project should provide a mechanism for
users to download(copy) transfers to their chosen download path.
Change-Id: Ide109fadb950ce7ab096c052c0a54ad4d215a9a1
Also check repo pointer in conversationRepository. If the conversation
is not correctly cloned (can be caused by a lot of things during the clone),
the infos will be invalid, so avoid to crash in this case.
Change-Id: I42a15200a06ca700bac972deea4cfc07ae87cae8
GitLab: #568
If the ICE is closed during the cacheSIPConnection, the sip transport
will not be found causing a potential crash
Change-Id: Ic2e7ab9272a2eb3274256151e37c2acd208cb0dd
GitLab: #569
Media direction attribute in the SDP should be set to "sendonly"
when the call is put on-hold.
Gitlab: #553
Change-Id: Iad82bf1fcac703bd275e857f28d1a4aa7323cc0d
Because no more devices can exists after an import, the swarm MUST be able to
sync from known conversation's members.
Change-Id: Ic22ec813b303815ce62b45fea6ab317ab3ba3147
fetched check the devices who has fetched since the last commit. With this file
we can detect if a device needs to fetch and if it's the case we start a connection.
cacheSipConnection will sync the conversations when called. This avoids the
daemon to connect too all contacts
Change-Id: Id85db09c3c0a6aa44dd48b3bbee5ed7e0a5d6b84
add API to ask for a failed transfer. This can be used when the
client detects a transfer they doesn't have yet. It will ask all
members of the conversation to send the transfer back.
GitLab: #136
Change-Id: I1484298c4fa0eabb614132e22d8032612e14b949
Sometimes a non swarm can send a text message via the DHT but not the trust
request confirm. In this case, the discussion must use the old path.
Change-Id: Id0d5223c830abe0840bef167b4be50abc276a72c
Pass all methods in async and on the io pool if they write into
the repository. Moreover, now MessageReceived guarantees to be
ordered if announced. e.g. if a parrallel merge and commit are done
previously if the merge was done before the commit you could receives
MessageReceived(merge) after MessageReceived(commit). Now it's
impossible. So the linearizedParent is guaranteed to be announced
before.
Change-Id: If4b94f19f5bf5abd4841fc19074231e3411e077d
If a TrustRequest is confirmed without conversationId this means
that the contact don't support swarm. So, we can drop the
conversation and fallback on old path.
Change-Id: Ic8238312fe79e10f340460d20880dbfc8dccf3f7
