From: Chris Marusich <cmmarusich@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCHES] gnu: linux-libre: Update to 4.16
Date: Sun, 08 Apr 2018 17:35:01 -0700 [thread overview]
Message-ID: <878t9xnrnu.fsf@gmail.com> (raw)
In-Reply-To: <87zi2dsp7y.fsf@netris.org> (Mark H. Weaver's message of "Sun, 08 Apr 2018 11:16:33 -0400")
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> So, we still have a decision to make: whether to delete these generated
> files (possibly in a snippet) to avoid using pre-generated non-source
> files in our build. I would be in favor of it.
>
> I'd like to hear opinions on this.
Perhaps we can consider our existing packages as a precedent. Many
packages include files in their source distribution that were
auto-generated by the Autotools. For example, consider the "configure"
script that Autoconf generates. Is there a significant difference
between the "configure" script and the "pre-generated non-source files"
you're talking about?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-04-09 0:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 18:36 [PATCHES] gnu: linux-libre: Update to 4.16 Mark H Weaver
2018-04-07 21:06 ` Leo Famulari
2018-04-08 1:10 ` Mark H Weaver
2018-04-08 8:28 ` Vincent Legoll
2018-04-08 15:16 ` Mark H Weaver
2018-04-09 0:35 ` Chris Marusich [this message]
2018-04-09 15:38 ` Ludovic Courtès
2018-05-09 6:44 ` Chris Marusich
2018-05-09 8:56 ` Ricardo Wurmus
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=878t9xnrnu.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).