unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Peter Šurda" <surda@economicsofbitcoin.com>
To: guix-devel@gnu.org, contact.ng0@cryptolab.net,
	chicks@getbackinthe.kitchen
Subject: Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT
Date: Fri, 17 Feb 2017 17:25:34 +0100	[thread overview]
Message-ID: <20170217162534.GD8688@mutt.economicsofbitcoin.com> (raw)
In-Reply-To: <20170217110502.GC8688@mutt.economicsofbitcoin.com>

(crossposting to the mailing list and participants)

I managed to get Guix running in a VM and updated the instructions
on the bitmessage wiki for Guix:
https://bitmessage.org/wiki/Compiling_instructions#Resolve_dependencies

(last row in the table). Based on this, whoever maintains the package
should be able to update it.

I haven't actually tested OpenCL because building pyopencl requires
opencl libraries and I have no idea how to install them on Guix. I don't
even think that open source drivers are compatible with the current CL
kernel, I was only ever able to get it running on closed source drivers
(AMD/Nvidia/Intel).

PyBitmessage is now compatible with both openssl 1.0.x and 1.1.x
(actually it should work back until 0.9.8b but I haven't tested it), and
in the next days I'll merge LibreSSL support so if you have to choose a
particular version or something, it doesn't matter, it will work with
whatever is installed.

On Fri, Feb 17, 2017 at 12:05:02PM +0100, Peter Šurda wrote:
>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.

-- 
Peter Šurda
Bitmessage core developer

  parent reply	other threads:[~2017-02-17 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 16:38 [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT Peter Šurda
     [not found] ` <20170217110502.GC8688@mutt.economicsofbitcoin.com>
2017-02-17 16:25   ` Peter Šurda [this message]
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

  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=20170217162534.GD8688@mutt.economicsofbitcoin.com \
    --to=surda@economicsofbitcoin.com \
    --cc=chicks@getbackinthe.kitchen \
    --cc=contact.ng0@cryptolab.net \
    --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 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).