From: Danny Milosavljevic <dannym@scratchpost.org>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add dtc.
Date: Mon, 29 Aug 2016 19:02:14 +0200 [thread overview]
Message-ID: <20160829190214.00dc91a2@scratchpost.org> (raw)
In-Reply-To: <CAL1_im=P-jVdT9r5OYgHRqsGVNue6ntEA_epSvxNtKUvw1JH8w@mail.gmail.com>
On Mon, 29 Aug 2016 16:53:10 +0200
David Craven <david@craven.ch> wrote:
> I made some stylistic changes, updated the license, updated to 1.4.1,
> removed the patches (checked the arch package and the nixos package,
> both don't patch dtc)
>
> I forgot to add u-boot.scm to local.mk...
>
> Danny, WDYT? Is it an improvement?
Back then, I cut it down to two patches only: one to build the documentation (just nice to have) and one to add "fdt_first_subnode" and "fdt_next_subnode" to the exports so you can actually traverse device trees yourself. That's necessary because they use a version script that defaults everything to local (exports nothing but their listed symbols).
While I almost always look up documentation online, the latter patch is kinda important. Debian patches it still.
So I'd include these two patches only. I'm not sure why they don't make a new release with this fix.
The name "device-tree-compiler" was also from Debian - they renamed it from "dtc" due to naming conflict. There's also a dtc bundled with the Linux kernel. So I'm fine with either name.
next prev parent reply other threads:[~2016-08-29 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 14:48 [PATCH] gnu: Add dtc David Craven
2016-08-29 14:53 ` David Craven
2016-08-29 17:02 ` Danny Milosavljevic [this message]
2016-08-29 16:16 ` [PATCH] gnu: Add u-boot David Craven
2016-08-29 18:27 ` Danny Milosavljevic
2016-08-29 18:30 ` Danny Milosavljevic
2016-08-31 20:40 ` Ludovic Courtès
2016-08-31 20:55 ` Danny Milosavljevic
2016-08-31 21:07 ` David Craven
2016-09-01 12:11 ` Ludovic Courtès
2016-08-31 20:44 ` [PATCH] gnu: Add dtc Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160829190214.00dc91a2@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=david@craven.ch \
--cc=guix-devel@gnu.org \
/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://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).