From: Thomas Danckaert <post@thomasdanckaert.be>
To: me@tobias.gr
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add xinetd.,Re: [PATCH] gnu: Add xinetd.
Date: Thu, 26 Jan 2017 15:55:36 +0100 (CET) [thread overview]
Message-ID: <20170126.155536.1839657954470559729.post@thomasdanckaert.be> (raw)
In-Reply-To: <46c3ce0a-22fd-5235-2c52-9ee7c3f8aa2b@tobias.gr>
From: Tobias Geerinckx-Rice <me@tobias.gr>
Subject: Re: [PATCH] gnu: Add xinetd.,Re: [PATCH] gnu: Add xinetd.
Date: Thu, 26 Jan 2017 14:58:53 +0100
> [...]
>> + (file-name (string-append name "-" version))
>
> file-name is used mainly to avoid polluting the store with
> meaningless
> (tobias.gr/download.php?foo=123) or misleading file names.
>
> It shouldn't be needed here, and would require its own ".tar.gz"
> suffix
> otherwise.
Ah yes, for some reason I thought we insisted the file would conform
to the version number as written here (i.e. "." instead of "-" as a
separator), and then forgot about the suffix...
> Would the simpler (and more idiomatic)
>
> #:tests? #f ... ; no tests
>
> work?
totally!
>> + (license (l:non-copyleft "file://COPYRIGHT"))))
>
> Interesting licence. :-) Against my intuition, it appears to be
> FSDG-compatible[0].
Yes, feels like this license can cause more confusion than it manages
to avoid (which is ostensibly the purpose) :-)
Thomas
next prev parent reply other threads:[~2017-01-26 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 10:43 [PATCH] gnu: Add xinetd Thomas Danckaert
2017-01-26 13:58 ` Tobias Geerinckx-Rice
2017-01-26 14:55 ` Thomas Danckaert [this message]
2017-01-26 15:00 ` [PATCH] gnu: Add xinetd.,Re: " Thomas Danckaert
2017-01-30 22:38 ` Leo Famulari
2017-01-31 7:49 ` Thomas Danckaert
2017-01-31 20:10 ` Leo Famulari
2017-01-31 20:27 ` Thomas Danckaert
2017-02-01 22:25 ` 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=20170126.155536.1839657954470559729.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).