From: ng0 <ng0@libertad.pw>
To: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: Add c-toxcore.
Date: Sun, 18 Dec 2016 08:51:20 +0000 [thread overview]
Message-ID: <87twa1oc1j.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161217190105.GD1726@jasmine>
Leo Famulari <leo@famulari.name> writes:
> On Thu, Dec 15, 2016 at 07:14:14PM +0000, ng0 wrote:
>> * gnu/packages/messaging.scm (c-toxcore): New variable.
>
>> + (version "0.1.0")
>
> I see a new release:
>
> https://github.com/TokTok/c-toxcore/tree/v0.1.1
They release very quickly. I can only update this on monday if
I'm lucky, possibly later. It's okay if we add the 0.1.0 and
update afterwards I think.
>> + (source
>> + (origin
>> + (method url-fetch)
>> + (uri (string-append "https://github.com/TokTok/c-toxcore/archive/v"
>> + version ".tar.gz"))
>
> Is this the canonical source of c-toxcore? What is its relationship to
> <https://github.com/irungentoo/toxcore>?
Yes, see toktok.github.io or what it was. c-toxcore seems to be
where every client is moving to, why how and what reasons there
are that it came to be, I'm not really interested in. There's
just a pull request to change to c-toxcore for every client, but
not all of them yet I think. So we need both at the moment.
>> + (arguments
>> + `(#:phases
>> + (modify-phases %standard-phases
>> + (add-after 'unpack 'autoconf
>> + (lambda _
>> + (zero? (system* "autoreconf" "-vfi")))))
>
> Is there no bootstrapped tarball? Okay if not, I'm just wondering.
Sadly no.
--
♥Ⓐ ng0 | PGP keys and more: https://n0is.noblogs.org/
| http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-18 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 19:14 [PATCH] utox update, c-toxcore new package ng0
2016-12-15 19:14 ` [PATCH 1/2] gnu: Add c-toxcore ng0
2016-12-17 19:01 ` Leo Famulari
2016-12-18 8:51 ` ng0 [this message]
2016-12-15 19:14 ` [PATCH 2/2] gnu: utox: Update to 0.11.0 ng0
2016-12-17 19:02 ` Leo Famulari
2016-12-18 8:54 ` 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=87twa1oc1j.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--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).