unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: 70433@debbugs.gnu.org
Subject: bug#70433: customize-kernel does not accept inferior package
Date: Wed, 17 Apr 2024 10:37:42 +0200	[thread overview]
Message-ID: <87il0g75bd.fsf@elephly.net> (raw)
In-Reply-To: <87o7a8763f.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 17 Apr 2024 10:20:52 +0200")

Ricardo Wurmus <rekado@elephly.net> writes:

> Especially on underpowered aarch64 systems with custom kernels it may be
> desirable to avoid rebuilding the kernel on "guix deploy" or "guix
> system reconfigure".  It's possible to use an inferior to pin the kernel
> to a known good version.
>
> Unfortunately, this doesn't work when attempting to customize the kernel
> with "customize-kernel" as that procedure doesn't accept an inferior as
> an input package.

"customize-kernel" works by inheriting from a base package.  It then
augments the arguments.

Inheriting from an inferior package does not work, though.  Nor is there
a procedure to obtain the arguments of an inferior package.  The naïve
approach of simply defining inferior-package-arguments fails:

--8<---------------cut here---------------start------------->8---
    (define (inferior-package-arguments package)
      "Return the arguments field of PACKAGE."
      (inferior-package-field package 'package-arguments))

    ...

    (inferior-package-arguments linux-libre-arm64-generic/fixed)
    ice-9/boot-9.scm:1685:16: In procedure raise-exception:
    socket:20:156: Unknown # object: "#<"
--8<---------------cut here---------------end--------------->8---


-- 
Ricardo




      reply	other threads:[~2024-04-17  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  8:20 bug#70433: customize-kernel does not accept inferior package Ricardo Wurmus
2024-04-17  8:37 ` Ricardo Wurmus [this message]

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=87il0g75bd.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=70433@debbugs.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).