From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnunet-gtk: adds --with-gnunet to configure-flags
Date: Tue, 8 Mar 2016 18:22:23 +0100 [thread overview]
Message-ID: <idjwppcx4ts.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87twkh81r0.fsf@grrlz.net>
Nils Gillmann <niasterisk@grrlz.net> writes:
> I'll ask on gnunet-dev about this, but it might be that we have
> to decide wether to default to some svn of gnunet, as 0.10.1 is
> really old. Stable, but old.. Which possibly could affect the
> experience for people who try to use gnunet now, before any
> applications like secushare are running on it. plus you need -svn
> if you want to hack on or testrun application which develop on
> top of / inside gnunet.
>
> Guix should provide a stable experience, but if stable means too
> old to deliver a useable experience of an still in development
> network, what do we suggest? I would not replace gnunet and
> gnunet-gtk, I would just make gnunet-svn the default (gnunet will
> default to gnunet-svn) and gnunet-0.10.1 will have to be
> installed explicitly.
> There are only a few open bugs until the next GNUnet release will
> be done, but 0.10.1 is just terribly old.
The reply to my bug report said something similar. If version 0.10.1 is
so old that upstream suggest taking the latest from SVN I suppose we
should do this too.
I do hope there will be a new release soon, though, as I don’t like to
use some arbitrary SVN checkout.
~~ Ricardo
next prev parent reply other threads:[~2016-03-08 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 23:58 [PATCH] gnunet-gtk: adds --with-gnunet to configure-flags Nils Gillmann
2016-03-08 14:48 ` Nils Gillmann
2016-03-08 15:47 ` Jookia
2016-03-08 17:22 ` Ricardo Wurmus [this message]
2016-03-08 17:58 ` Nils Gillmann
2016-03-09 17:52 ` Andreas Enge
2016-03-09 18:16 ` Nils Gillmann
2016-03-09 18:30 ` Jookia
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=idjwppcx4ts.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=niasterisk@grrlz.net \
/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).