From: "Peter Šurda" <surda@economicsofbitcoin.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT
Date: Thu, 16 Feb 2017 17:38:04 +0100 [thread overview]
Message-ID: <20170216163803.GA12299@mutt.economicsofbitcoin.com> (raw)
On Wed, 15 Feb 2017 19:33:05, ng0 wrote:
> PyBitmessage doesn't build from git commits here. I nfact, there
> wasn't much public activity in upstream in the last months since the
> last release. We use the tarballs.
PyBitmessage is being developed in the v0.6 branch, that's where you'll
find the commits. The previous comment regarding new dependency on
msgpack was correct. v0.6.2 is planned on being released by the end of
the month. I'll be happy to assist but I'm not on this list, I just
monitor the web for mentions of "bitmessage". For discussing development
of Bitmessage, I recommend using one of the following, in this order:
- The "bitmessage" chan on bitmessage
- https://bitmessage.slack.org
- #bitmessage on freenode
For easier resolving of dependencies, the latest code can also detect
more accurately what sort of OS (including several linux distributions
and BSD variants) it's running on and makes a recommendation for what to
do with your package manager based on that. I don't have GNU Guix in my
test environment now. I can add it but may need assistance as I'm not
familiar with it.
You can also submit a pull request, here are the contribution
guidelines:
https://bitmessage.org/wiki/Contribute
--
Peter Šurda
Bitmessage core developer
next reply other threads:[~2017-02-16 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 16:38 Peter Šurda [this message]
[not found] ` <20170217110502.GC8688@mutt.economicsofbitcoin.com>
2017-02-17 16:25 ` [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT Peter Šurda
2017-02-17 16:41 ` ng0
2017-02-17 17:19 ` Peter Šurda
2017-02-17 17:53 ` ng0
2017-02-17 19:33 ` Peter Šurda
2017-02-17 19:40 ` ng0
2017-02-17 20:06 ` Peter Šurda
2017-02-17 20:14 ` ng0
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170216163803.GA12299@mutt.economicsofbitcoin.com \
--to=surda@economicsofbitcoin.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.