From: "José Pekkarinen" <jose.pekkarinen@unikie.com>
To: Alyssa Ross <hi@alyssa.is>
Cc: Ville Ilvonen <ville.ilvonen@unikie.com>,
devel@spectrum-os.org,
Ivan Nikolaenko <ivan.nikolaenko@unikie.com>
Subject: Re: [PATCH 1/4] Introduce a build configuration file
Date: Thu, 8 Sep 2022 14:39:46 +0300 [thread overview]
Message-ID: <CAJPV9Mpa0Cv+omZ2Xs8rabfPk4o--uXBXoEco+iZ_RRqWzag0g@mail.gmail.com> (raw)
In-Reply-To: <87fsh5c60x.fsf@alyssa.is>
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
On Tue, Sep 6, 2022 at 10:32 AM Alyssa Ross <hi@alyssa.is> wrote:
> Ville Ilvonen <ville.ilvonen@unikie.com> writes:
>
> > On 8/31/22 12:37, Alyssa Ross wrote:
> >> By default, a file called "config.nix" in the root of the Spectrum
> >> repository will be read if it exists. That file should contain an
> >> attribute set. Currently, only a "pkgs" key is supported, which
> >> allows specifying a custom package set that will be used throughout
> >> the Spectrum Nix files. This will allow us to provide configuartion
> >> options for people who want to build Spectrum in ways that are
> >> probably not suitable for upstreaming.
> > >
> >> For example, using the "pkgs" config option I'm introducing here, it
> >> would be possible to use an overlay to patch individual components,
> >> like so:
> >>
> >> {
> >> pkgs = import <nixpkgs> {
> >> overlays = [
> >> (final: super: {
> >> weston = super.weston.overrideAttrs ({ patches ? [], ...
> }: {
> >> patches = patches ++ [
> >> path/to/weston.patch
> >> ];
> >> });
> >> })
> >> ];
> >> };
> >> }
> >>
> >> Signed-off-by: Alyssa Ross <hi@alyssa.is>
>
Tested-by: José Pekkarinen <jose.pekkarinen@unikie.com>
>> ---
> >
> > Appreciate it as this makes it more clean to implement device specifics.
> > Would you like to see the device specific configs in tree or out of
> > tree? One option would be to set the default config and support in tree
> > configs of devices people could choose from. Even if not fully supported
> > by upstream, they could be useful as examples. If both are possible,
> > criteria for guiding in-tree and out-of-tree configs could be also
> useful.
>
> I'm not sure yet. Let's maybe revisit once we have generic ARM support
> in-tree, and see how it feels then?
>
> > Thanks,
> >
> > -Ville
> >
> > Reviewed-by: Ville Ilvonen <ville.ilvonen@unikie.com>
>
> Thanks for the review. :)
>
--
José.
[-- Attachment #2: Type: text/html, Size: 3430 bytes --]
next prev parent reply other threads:[~2022-09-08 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 9:37 [PATCH 1/4] Introduce a build configuration file Alyssa Ross
2022-08-31 9:37 ` [PATCH 2/4] nix: prefer build configs from <spectrum-config> Alyssa Ross
2022-09-08 11:40 ` José Pekkarinen
2022-09-14 6:58 ` Alyssa Ross
2022-08-31 9:37 ` [PATCH 3/4] Documentation/jekyll: patch for AsciiDoc examples Alyssa Ross
2022-09-14 7:03 ` Alyssa Ross
2022-08-31 9:37 ` [PATCH 4/4] Documentation: document build configuration file Alyssa Ross
2022-09-14 6:58 ` Alyssa Ross
2022-09-06 5:53 ` [PATCH 1/4] Introduce a " Ville Ilvonen
[not found] ` <87fsh5c60x.fsf@alyssa.is>
2022-09-08 11:39 ` José Pekkarinen [this message]
2022-09-14 6:58 ` Alyssa Ross
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJPV9Mpa0Cv+omZ2Xs8rabfPk4o--uXBXoEco+iZ_RRqWzag0g@mail.gmail.com \
--to=jose.pekkarinen@unikie.com \
--cc=devel@spectrum-os.org \
--cc=hi@alyssa.is \
--cc=ivan.nikolaenko@unikie.com \
--cc=ville.ilvonen@unikie.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://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
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 NNTP newsgroup(s).