Re: [GNU-linux-libre] Replacing Yocto with Guix kernel image builds: best practices

[Ricardo Wurmus <rekado@elephly.net>]

Begley Brothers Inc <begleybrothers@gmail.com> writes:

> > You can either put your config files in a separate git repository and add
> > that to
> > the native inputs, or you can include the config files in your channel
> > repository (or later in Guix itself).
> >
>
> Thanks for the suggestion.  That gives some assurance.
> Could you point to an existing guix (upstream) package that is a best
> practice
> example of each of those two approaches?
> - accessing files from a separate repo
> - a guix (upstream) package using other files

There are many examples in the Guix repository.  One example is
java-cisd-args4j in gnu/packages/java.scm, which has “build-resources”
as a native-input, which is an SVN origin.

> Can "add it to their ~/.config/guix/channels.scm file" be scripted as part
> of the
> package?
> Is there an example of a guix (upstream) package that does this?

No, channel configuration is a user action.  The channel would be the
thing that provides your package in the first place.

But since you want to add your package variants to Guix itself a
discussion of channels isn’t really interesting.

-- 
Ricardo