On Thu, May 16, 2019, Mark H Weaver wrote:
> Marius Bakke <mba...@fastmail.com> writes:
>
> > I just want to point out an (IMO) easier way to provide a custom kernel
> > configuration, that does not involve the "make-linux-libre" procedure:
> >
> > (define-public linux-libre/custom
> > (package
> > (inherit linux-libre)
> > (native-inputs
> > `(("kconfig" ,(local-file "kernel.config"))
> > ,@(alist-delete "kconfig"
> > (package-native-inputs linux-libre))))))
> >
> > At the end of the day, Linux-Libre is just a regular package that can be
> > inherited and overridden like any other :-)
>
> I think this is the approach we should promote for now. I would prefer
> to leave 'make-linux-libre' as an internal implementation detail, and
> hopefully one with a limited life span.
Is it also possible to leave make-linux-libre out of the 2nd method presented in
the blog? I can't see any way to modify extra-options without it since in the
package it appears deeply nested inside arguments.
