From: David Craven <david@craven.ch>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] system: Remove spec->file-system.
Date: Sat, 3 Dec 2016 00:23:57 +0100 [thread overview]
Message-ID: <CAL1_im=pbf5Wj2ueHKENHKXTBA1JLM15onXD4M+HpQ234hjPzw@mail.gmail.com> (raw)
In-Reply-To: <20161202183716.25174-1-david@craven.ch>
The reason I'm suggesting to remove this function, is because it seems
like any case one would want to use it, one should not be using it.
There is a separation of gnu/system and gnu/build and a
spec->file-system function encourages people to try using the
<file-system> in the build part. I think that it's a "code smell" as
the one instance where it was used is dubious.
next prev parent reply other threads:[~2016-12-02 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 18:37 [PATCH] system: Remove spec->file-system David Craven
2016-12-02 23:23 ` David Craven [this message]
2016-12-04 15:48 ` Ludovic Courtès
2016-12-04 16:19 ` David Craven
2016-12-05 20:58 ` 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='CAL1_im=pbf5Wj2ueHKENHKXTBA1JLM15onXD4M+HpQ234hjPzw@mail.gmail.com' \
--to=david@craven.ch \
--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).