From: zerodaysfordays@sdf.lonestar.org (Jakob L. Kreuze)
To: 36638@debbugs.gnu.org
Subject: [bug#36638] [PATCH 0/2] gnu: Add i2pd.
Date: Sat, 13 Jul 2019 13:52:38 -0400 [thread overview]
Message-ID: <87o91xbz4p.fsf@sdf.lonestar.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
I hope that creating an entirely new file for this isn't too intrusive.
My thinking is that, when the upstream Java implementation of the I2P
daemon is packaged, it can go in 'i2p.scm', along with any related
packages such as I2P-Bote.
Jakob L. Kreuze (2):
gnu: Add websocketpp.
gnu: Add i2pd.
gnu/local.mk | 1 +
gnu/packages/i2p.scm | 85 ++++++++++++++++++++++++++++++++++++++++++++
gnu/packages/web.scm | 28 +++++++++++++++
3 files changed, 114 insertions(+)
create mode 100644 gnu/packages/i2p.scm
--
2.22.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2019-07-13 17:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-13 17:52 Jakob L. Kreuze [this message]
2019-07-13 17:53 ` [bug#36638] [PATCH 1/2] gnu: Add websocketpp Jakob L. Kreuze
2019-07-13 17:54 ` [bug#36638] [PATCH 2/2] gnu: Add i2pd Jakob L. Kreuze
2019-07-15 16:29 ` Ludovic Courtès
2019-07-15 16:21 ` [bug#36638] [PATCH 1/2] gnu: Add websocketpp Ludovic Courtès
2019-07-15 16:31 ` Ludovic Courtès
2019-07-16 16:48 ` Jakob L. Kreuze
2019-07-17 18:10 ` [bug#36638] [PATCH v2 0/2] gnu: Add i2pd Jakob L. Kreuze
2019-07-17 18:11 ` [bug#36638] [PATCH v2 1/2] gnu: Add websocketpp Jakob L. Kreuze
2019-07-17 18:12 ` [bug#36638] [PATCH v2 2/2] gnu: Add i2pd Jakob L. Kreuze
2019-07-18 9:27 ` Ludovic Courtès
2019-07-18 9:18 ` [bug#36638] [PATCH v2 1/2] gnu: Add websocketpp Ludovic Courtès
2019-07-18 9:20 ` Ludovic Courtès
2019-07-18 9:29 ` [bug#36638] [PATCH v2 0/2] gnu: Add i2pd Ludovic Courtès
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=87o91xbz4p.fsf@sdf.lonestar.org \
--to=zerodaysfordays@sdf.lonestar.org \
--cc=36638@debbugs.gnu.org \
/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).