Guix lacks ability to customize guix package that gets installed as part of main guix channel

  • Open
  • quality assurance status badge
Details
One participant
  • Gordon Quad
Owner
unassigned
Submitted by
Gordon Quad
Severity
normal
G
G
Gordon Quad wrote on 2 Feb 2022 12:09
(address . bug-guix@gnu.org)
20220202110945.ts55ny7kk2pl54ed@citadel.info
According to configure.ac script in guix repo guile-avahi dependency is
optional, and guix package definition has cross-compilation exceptions
for guile-avahi, meaning guix surely can be built without it.

However those checks are hardcoded and there is no way of specifying
that I want to build guix w/o guile-avahi if I am just doing a mere guix pull.

I can make my own package definition for guix by inheriting guix package
and remove guile-avahi dependency but there is no way to supply that
package definition instead of original guix for guix pull.

Moreover there is no simple way to customize guix by doing guix fork
since all the commits are authenticated, which means I either have to
give up authentication completely not only for guix channel but for every
other channel by doing guix pull --disable-authentication or I have to
re-sign every single commit in my local guix repo fork.

I understand that it is part of security model but it is also a
significant obstacle for intent of utilizing the ability to turn
optional dependency off and not have bunch of extra stuff installed on
my system that I don't need.

Perhaps there should be another mechanism for customizing guix from guix
channel?
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 53719@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 53719
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch