unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCHES] gnu: linux-libre: Update to 4.16
Date: Tue, 08 May 2018 23:44:35 -0700	[thread overview]
Message-ID: <8736z11g6k.fsf@gmail.com> (raw)
In-Reply-To: <87in90ie47.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 09 Apr 2018 17:38:48 +0200")

[-- Attachment #1: Type: text/plain, Size: 1958 bytes --]

ludo@gnu.org (Ludovic Courtès) writes:

> Hello,
>
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> 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.
>
> I’d be in favor of removing these, especially since that seems to be an
> easy change, but…
>
>> 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?
>
> Indeed, there’s a long tradition in GNU to ship generated code to
> facilitate bootstrapping.  There’s configure, Makefile.in, etc., and
> there’s also Bison- and Flex-generated files often.
>
> I have mixed feelings about this.  I think it’s great to be able to use
> these pre-generated files; our bootstrap graph would be much more
> complicated or even out of reach if we were to re-generate everything.
> OTOH, it’s true that this is the elephant in the room in terms of
> bootstrapping.
>
> Maybe it’s a can of worms we’d rather leave aside.  :-)
>
> Thoughts?

Given the profound silence on this topic, I am inclined to agree with
you that it's a can of worms we'd rather leave aside.  Therefore, I
think we should do whatever is most practical, so I am happy to defer to
Mark on this.  If it's easy to remove the auto-generated files, I see no
reason for us to avoid removing them.  If it's difficult to remove the
auto-generated files, I don't think we should bend over backwards to
remove them.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-05-09  6:44 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
2018-04-09 15:38           ` Ludovic Courtès
2018-05-09  6:44             ` Chris Marusich [this message]
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=8736z11g6k.fsf@gmail.com \
    --to=cmmarusich@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).