And now both libringclient and ring-client-gnome build!
Sadly gnome-ring fails to start:
--8<---cut here---start->8---
> /gnu/store/6q1ysbyki4v1zidbcndvyrchm3jncs58-ring-client-gnome-20190108.1.8659b2c/bin/gnome-ring
> --debug
GLib-GIO-Message: 19:30:42.058
Pierre Neidhardt skrev: (10 januari 2019 14:19:34 CET)
>
>swedebugia writes:
>> I put it in messaging.scm. Is that suitable?
>
>Maybe not. From qaul.net:
>
>> qaul.net implements a redundant, open communication principle, in
>which
>> wireless-enabled computers and mobile devices can directly fo
> Now I'm onto pjproject. I'll publish my work later today and if I get stuck
> then everyone is welcome to look into it :D
OK, I'm making progress. I've pushed some updates on master.
So basically all we need at this stage, I think, is a
an up-to-date, patched definition of pjproject.
The p
Pierre Neidhardt skrev: (10 januari 2019 10:10:38 CET)
>
>> I started packaging qual (qual.net)
>
>Did you mean "qaul.net"?
Yes 😅
It seems promising, but I never tried it IRL.
I put it in messaging.scm. Is that suitable?
--
Sent from my p≡p for Android.
pEpkey.asc
Description: application/pgp
Hi Pierre,
Pierre Neidhardt writes:
>> If there is no longer a 'Ring' project, then let's rule this out.
>
> The current state of affair is not so black & white: It's "Jami" on the web
> page, but everything else is stilled called "Ring": the library, the
> daemon, and
> I'm unsure about the cli
On 2019-01-10 05:17, swedebugia wrote:
Pierre Neidhardt skrev: (9 januari 2019 19:14:38 CET)
Jami is made of 3 packages and might drag in 2-3 packages that
so far are not used by any other package.
General question: where should those packages go?
- ring.scm
- jami.scm
Pierre Neidhardt skrev: (9 januari 2019 19:14:38 CET)
>Jami is made of 3 packages and might drag in 2-3 packages that
>so far are not used by any other package.
>
>General question: where should those packages go?
>
>- ring.scm
>- jami.scm
>- telephony.scm
>
>?
Hi Pierre.
I think we should put th
> If there is no longer a 'Ring' project, then let's rule this out.
The current state of affair is not so black & white: It's "Jami" on the web
page, but everything else is stilled called "Ring": the library, the daemon, and
I'm unsure about the client itself.
It might change in the future.
On Wed, Jan 09, 2019 at 07:14:38PM +0100, Pierre Neidhardt wrote:
> Jami is made of 3 packages and might drag in 2-3 packages that
> so far are not used by any other package.
>
> General question: where should those packages go?
>
> - ring.scm
If there is no longer a 'Ring' project, then let's r
Jami is made of 3 packages and might drag in 2-3 packages that
so far are not used by any other package.
General question: where should those packages go?
- ring.scm
- jami.scm
- telephony.scm
?
OK, thanks for the details. Now back to work and fingers crossed! :)
Hi Pierre,
Pierre Neidhardt writes:
> Hi Tim!
>
> Thanks for sharing!
> Adonay Felipe Nogueira initial patch is now 2 years old, but it's already been
> very helpful.
>
> I've noticed the thing about the ring-specific patches. I'm not sure but it
> seems that beside pjproject, none of them are
Hi Pierre,
Pierre Neidhardt writes:
> Hey,
>
> I'd like to package Jami. Has anyone given it a shot yet?
I did some work on this about eight months ago, but wasn’t able to
finish it. AFAIK, my work is the most recent and complete attempt.
IIRC, I could install and run Ring, but it was not ent
Hello Pierre,
Pierre Neidhardt ezt Ãrta (idÅ‘pont: 2019. jan. 9.,
Sze, 9:50):
>
> Hey,
>
> I'd like to package Jami. Has anyone given it a shot yet?
>
This would be really nice.
I believe you can find some old bugs related to this, but it was
called Ring then.
I don't know if those are releva
Hey,
I'd like to package Jami. Has anyone given it a shot yet?
15 matches
Mail list logo
