all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Peter Šurda" <surda@economicsofbitcoin.com>
To: guix-devel@gnu.org, chicks@getbackinthe.kitchen,
	ng0 <contact.ng0@cryptolab.net>
Subject: Re: [PATCH] gnu: Add pybitmessage, [PATCH] gnu: Add python2-pyqt-4, [PAT
Date: Fri, 17 Feb 2017 21:06:27 +0100	[thread overview]
Message-ID: <20170217200627.GG8688@mutt.economicsofbitcoin.com> (raw)
In-Reply-To: <20170217194026.lpuh45lv2xk2nmbq@wasp>

On Fri, Feb 17, 2017 at 07:40:26PM +0000, ng0 wrote:
>I think you are trying to do to much, to be honest. Leave the job of
>system integration up to the people who are familar with the systems.
Based on my experience, without instructions, they often don't do it
correctly. They miss some of the dependencies which then results in
disabled features and then I have to deal with that. That's the purpose
of the wiki page linked earlier.

>We have the guix package already, no point in trying to re-invent it.
>Gentoo packagers know best what to do for Gentoo, same for Debian, the
>BSD folks, etc. No idea about Windows and OSX.
>What I tried to communicate here was, the instructions might be wrong
>and misleading. You didn't respond to my question, so I'll just leave
>you with this.
I guess I don't understand what you're looking for then.

-- 
Peter Šurda
Bitmessage core developer

  reply	other threads:[~2017-02-17 20:06 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
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 [this message]
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=20170217200627.GG8688@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 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.