From: taylanbayirli@gmail.com (Taylan Ulrich Bayırlı/Kammer)
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add scheme-bytestructures
Date: Tue, 11 Oct 2016 15:15:52 +0200 [thread overview]
Message-ID: <87fuo3f2lz.fsf@gmail.com> (raw)
In-Reply-To: <8760p0gcer.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 10 Oct 2016 22:46:36 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi Amirouche,
>
> Some comments to complement Kei’s.
>
> Kei Kebreau <kei@openmailbox.org> skribis:
>
>> Amirouche Boubekki <amirouche.boubekki@gmail.com> writes:
>>
>>> Warning: scheme-bytestructures works on various implementation of Scheme but this patch adds
>>> it only for guile-2.0.
>>>
>>> This is a pure scheme package there is no autotools that's why I use the trivial-build-system.
>>>
>>> This doesn't run the test suite, yet.
>>>
>>> From fb2eb7ffd88ec4fba09411195a54b59d67d9c137 Mon Sep 17 00:00:00 2001
>>> From: Amirouche <amirouche@hypermove.net>
>>> Date: Sun, 9 Oct 2016 12:31:20 +0200
>>> Subject: [PATCH] gnu: Add scheme-bytestructures
>>>
>>> * gnu/packages/guile.scm (scheme-bytestructures): New variable.
>>>
>>> diff --git a/gnu/packages/guile.scm b/gnu/packages/guile.scm
>>> index 0890f19..383990e 100644
>>> --- a/gnu/packages/guile.scm
>>> +++ b/gnu/packages/guile.scm
>>> @@ -1265,4 +1265,105 @@ is no support for parsing block and inline level HTML.")
>>> (define-public guile2.2-commonmark
>>> (package-for-guile-2.2 guile-commonmark))
>>>
>>> +(define-public scheme-bytestructures
>>> + (package
>>> + (name "scheme-bytestructures")
>
> I would suggest calling it “guile-scheme-bytestructures” (or
> “guile-bytestructures”?) to distinguish this package from the same one
> built for another implementation.
FWIW, second option sounds good to me (guile-bytestructures), speaking
as bytestructures author.
>>> + (license gpl3)))
>
> Probably ‘gpl3+’; could you check?
The intention is gpl3+ so if any file implies otherwise that's an error
on my end. I'm pretty sure I've used standard gpl3+ boilerplate
everywhere though.
Thanks all for doing this. :-)
Taylan
next prev parent reply other threads:[~2016-10-11 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 10:38 [PATCH] Add scheme-bytestructures Amirouche Boubekki
2016-10-10 17:51 ` Kei Kebreau
2016-10-10 20:46 ` Ludovic Courtès
2016-10-11 13:15 ` Taylan Ulrich Bayırlı/Kammer [this message]
2016-10-18 13:14 ` Amirouche Boubekki
2016-10-18 14:27 ` Ludovic Courtès
2016-10-19 7:18 ` Amirouche Boubekki
2016-10-20 14:00 ` Ludovic Courtès
2016-10-20 16:03 ` Amirouche Boubekki
2016-10-24 20:56 ` Ludovic Courtès
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=87fuo3f2lz.fsf@gmail.com \
--to=taylanbayirli@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).