From: Alyssa Ross <hi@alyssa.is>
To: Tero Tervala <tero.tervala@unikie.com>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH] Allow static building of dtc
Date: Fri, 20 May 2022 12:56:11 +0000 [thread overview]
Message-ID: <20220520125611.2b6tak7dgtssx2lb@eve> (raw)
In-Reply-To: <20220520095257.23038-1-tero.tervala@unikie.com>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Fri, May 20, 2022 at 12:52:57PM +0300, Tero Tervala wrote:
> Signed-off-by: Tero Tervala <tero.tervala@unikie.com>
> ---
> ...01-Use-libfdt.a-if-building-staticly.patch | 54 +++++++++++++++++++
> pkgs/development/compilers/dtc/default.nix | 4 ++
> 2 files changed, 58 insertions(+)
> create mode 100644 pkgs/development/compilers/dtc/0001-Use-libfdt.a-if-building-staticly.patch
Thanks for the patch! Since pkgsStatic.dtc is broken in upstream
Nixpkgs, would you mind submitting it there? [1] It will get us wider
review than on the Spectrum list, and if it's accepted upstream (I
imagine this or a similar fix will be) it'll minimize how much Spectrum
Nixpkgs diverges, which is important for maintainability. Once it's
accepted upstream (or if it ends up being difficult to upstream), we can
cherry-pick it into Spectrum's nixpkgs, or update Spectrum's nixpkgs to
a version that includes the fix.
When you open the Nixpkgs PR, please CC me. My GitHub username is
@alyssais. Nixpkgs is quite picky about commit message format, so make
sure to look at the examples in the documentation linked below.
When I get a chance, I'll update the documentation to recommend
submitting fixes to upstream Nixpkgs first if applicable.
[1]: https://nixos.org/manual/nixpkgs/unstable/#chap-submitting-changes
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-20 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 9:52 [PATCH] Allow static building of dtc Tero Tervala
2022-05-20 12:56 ` Alyssa Ross [this message]
2022-05-25 8:08 ` Tero Tervala
2022-05-25 20:02 ` 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=20220520125611.2b6tak7dgtssx2lb@eve \
--to=hi@alyssa.is \
--cc=devel@spectrum-os.org \
--cc=tero.tervala@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).