From: Timothy Sample <samplet@ngyro.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging Jami (ex GNU Ring)
Date: Wed, 09 Jan 2019 10:03:49 -0500 [thread overview]
Message-ID: <875zuxg9ey.fsf@ngyro.com> (raw)
In-Reply-To: <87imyy5i66.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Wed, 09 Jan 2019 09:50:09 +0100")
Hi Pierre,
Pierre Neidhardt <mail@ambrevar.xyz> 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 entirely usable.
I just committed all of my working directory files, and pushed
everything to <https://gitlab.com/samplet/guix.git> on the “wip-ring”
branch. Unfortunately, I have to kind of throw it over the wall at you.
It was some time ago, and I can’t remember all of the details.
Apologies for the mess. :)
There are two things that I do remember, though. (1) Jami has a lot of
vendored packages and some of them have significant patches (I’m mostly
thinking of “pjproject”). Some of these patches were in the process of
being upstreamed, so let’s hope that has gone well and you can clean up
some of the patches and hacks that were needed there. (2) I had some
pause about what to do with copyright headers. You are the fourth
person to work on this, and the other three of us did not consistently
add our names to the copyright headers of files we changed. ;) Not
sure what to do there.
Happy hacking!
-- Tim
next prev parent reply other threads:[~2019-01-09 15:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 8:50 Packaging Jami (ex GNU Ring) Pierre Neidhardt
2019-01-09 8:58 ` Gábor Boskovits
2019-01-09 9:03 ` Pierre Neidhardt
2019-01-09 15:03 ` Timothy Sample [this message]
2019-01-09 16:26 ` Pierre Neidhardt
2019-01-09 17:57 ` Timothy Sample
2019-01-09 18:10 ` Pierre Neidhardt
2019-01-09 18:14 ` Pierre Neidhardt
2019-01-09 19:18 ` Leo Famulari
2019-01-09 20:05 ` Pierre Neidhardt
2019-01-10 12:18 ` Maxim Cournoyer
2019-01-10 12:55 ` Pierre Neidhardt
2019-01-10 4:17 ` swedebugia
2019-01-10 5:41 ` swedebugia
2019-01-10 9:08 ` Pierre Neidhardt
2019-01-10 9:10 ` Pierre Neidhardt
2019-01-10 13:13 ` swedebugia
2019-01-10 13:19 ` Pierre Neidhardt
2019-01-10 20:13 ` Pierre Neidhardt
2019-01-11 15:02 ` swedebugia
2019-01-11 17:43 ` Pierre Neidhardt
2019-01-11 18:32 ` Pierre Neidhardt
2019-01-11 18:53 ` Pierre Neidhardt
2019-01-11 20:10 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zuxg9ey.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).