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: 32167@debbugs.gnu.org, pkill9@runbox.com
Subject: bug#32167: Kernel 'build' directory in the store is a broken symbolic link
Date: Mon, 23 Jul 2018 15:00:57 +0200	[thread overview]
Message-ID: <87k1pmrtrq.fsf@gnu.org> (raw)
In-Reply-To: <87r2k2u9bl.fsf@netris.org> (Mark H. Weaver's message of "Mon, 16 Jul 2018 18:03:58 -0400")

Hi,

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

> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> On Mon, 16 Jul 2018 18:55:11 +0100 (BST)
>> <pkill9@runbox.com> wrote:
>>
>>> It would be good to keep the build directory though, since it's
>>> expected to exist, and it's easier to just download a module's
>>> source and compile it and test it.
>>
>> I agree.
>>
>> /run/booted-system/kernel/lib/modules/4.17.3-gnu is in the store
>> anyway so it will be seen by the GC.
>>
>> The fix would be in linux-libre.
>
> If we were to preserve the kernel build directory as a store item, and
> keep a link from the modules directory to the build directory, that
> would greatly increase the size of the most minimal system that users
> could build.

Yeah, we shouldn’t do that IMO.

> If the intent here is to allow support for out-of-tree kernel modules,
> then fixing these symlinks would not solve the problem, and it's not
> clear to me that fixing them would be part of a proper solution on
> GuixSD.  GuixSD is not a system where you can simply compile a kernel
> module manually and install it, because our module directory is
> immutable.  If the goal is to support building out-of-tree kernel
> modules, that's a separate discussion that deserves its own "wishlist"
> bug report, I think.

I agree.

Ludo’.

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15 20:07 bug#32167: Kernel 'build' directory in the store is a broken symbolic link pkill9
2018-07-15 21:32 ` Nils Gillmann
2018-07-16 17:55 ` pkill9
2018-07-16 18:15   ` Danny Milosavljevic
2018-07-16 22:03     ` Mark H Weaver
2018-07-16 23:10       ` pkill9
2018-07-23 13:00       ` Ludovic Courtès [this message]
2021-09-25  0:51         ` Sarah Morgensen

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=87k1pmrtrq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32167@debbugs.gnu.org \
    --cc=mhw@netris.org \
    --cc=pkill9@runbox.com \
    /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).