[bug#34044] Packaging Jami (ex GNU Ring)

[Pierre Neidhardt]

Christopher Lemmer Webber <address@hidden> writes:

> I've compiled and run this.  I was able to install ring-client-gnome and
> get it up and running (I rebased against git master and it's fine) via
> `ring.cx`.  However, when I run it, it complains that it can't find the
> daemon and shuts down.  Any idea how to run that so I can test further?

If you run Gnome or KDE, the daemon should be started for you.
Otherwise, you've got to start it manually:

/gnu/store/...-libring.../lib/dring -dcp

This is a bit involved for the casual user, but arguably this should be
fixed upstream in the ring.cx script: I don't see why you need a desktop
environment to automate this.

> Also, there's a few TODOs that I'm not sure are still relevant in the
> ring-client-gnome definition:
>
>   ;; TODO: Don't prompt for root password on build?

I had this once but could not reproduce, so I guess it's safe to remove now.

>        ;; TODO: We must wrap ring-client-gnome to use
>        ;; sqlite-with-column-metadata or else it will fail with:
>        ;;
>        ;;   
> /gnu/store/...-qtbase-5.11.2/lib/qt5/plugins/sqldrivers/libqsqlite.so:
>        ;;   undefined symbol: sqlite3_column_table_name16
>        ;;
>        ;; qtbase is built against sqlite-with-column-metadata but somehow
>        ;; ring-client-gnome ends up with both sqlite and
>        ;; sqlite-with-column-metadata as inputs and it seems that
>        ;; libqsqlite.so gets confused.

This is still valid, if you look at the LD_LIBRARY_PATH wrapper around 
gnome-ring.
The thing is, it seems that qtbase is loading it's libraries at runtime
and gets confused between which one to pick as opposed to the libraries
it was linked against.  This doesn't make much sense to me.  I'd like to
understand more what's going on.

The wrappers works, but I'd rather leave the TODO: (or at least the
comment) until this has been properly fixed.

Thanks for testing!

signature.asc
Description: PGP signature