unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>,
	30537@debbugs.gnu.org
Subject: bug#30537: Grafts vs. early bootstrapping packages
Date: Fri, 23 Feb 2018 23:01:25 +0100	[thread overview]
Message-ID: <87muzz9xhm.fsf_-_@gnu.org> (raw)
In-Reply-To: <87bmgiey3k.fsf@netris.org> (Mark H. Weaver's message of "Wed, 21 Feb 2018 18:12:31 -0500")

Hello,

Mark H Weaver <mhw@netris.org> skribis:

>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:

[...]

>>  (define glibc-final
>>    ;; The final glibc, which embeds the statically-linked Bash built above.
>> -  (package (inherit glibc-final-with-bootstrap-bash)
>> +  (package/inherit glibc-final-with-bootstrap-bash
>>      (name "glibc")
>>      (inputs `(("static-bash" ,static-bash-for-glibc)
>>                ,@(alist-delete
>
> We seem to be oscillating on the question of whether to graft these
> early GLIBCs.  In June 2017, I switched to using 'package/inherit' here
> in commit 13f7f2fd2b208c29361ef2290f55911879a6adf2, and in October those
> changes were reverted in commit 848f550f2c105326dc3be4033c8aaf35ec21cde4
> by Efraim, although I'm not sure why.

I doesn’t make sense to graft “glibc-intermediate” because it’s only
used in ‘static-bash-for-glibc’, which statically links against it.  The
situation is similar with the “-boot0” packages: they are not referenced
by the packages we use.

So I think 848f550f2c105326dc3be4033c8aaf35ec21cde4 was a good idea.
f00b85ff8d34df0a1879e593d4a85629b8586af7 does something similar.

Ludo’.

  parent reply	other threads:[~2018-02-23 22:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 18:46 glibc 2.26 refuses to run on CentOS 6.8 Ricardo Wurmus
     [not found] ` <87d110stkn.fsf@mdc-berlin.de>
     [not found]   ` <87a7w4ssmx.fsf@mdc-berlin.de>
2018-02-19 19:41     ` bug#30537: " Ricardo Wurmus
     [not found]     ` <878tbosr7h.fsf@mdc-berlin.de>
2018-02-19 20:28       ` Jan Nieuwenhuizen
2018-02-21 23:12       ` Mark H Weaver
     [not found]       ` <87bmgiey3k.fsf@netris.org>
2018-02-22 20:30         ` Efraim Flashner
2018-02-23 22:01         ` Ludovic Courtès [this message]
2018-02-20  1:22 ` Leo Famulari
2018-02-20 11:52   ` Leo Famulari
2018-02-20 12:34     ` Ricardo Wurmus
2018-02-20 12:51       ` Leo Famulari
2018-02-20 14:33         ` Ricardo Wurmus
2018-02-20 17:55           ` Ricardo Wurmus
2018-02-20  9:39 ` Efraim Flashner
2018-02-23 22:26 ` 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=87muzz9xhm.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=30537@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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).