From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5 v2] package infra: add patch-dependencies
Date: Sun, 5 Apr 2015 11:46:24 +0200 [thread overview]
Message-ID: <20150405114624.1077fb67@free-electrons.com> (raw)
In-Reply-To: <20150405091656.GC4134@free.fr>
Dear Yann E. MORIN,
On Sun, 5 Apr 2015 11:16:56 +0200, Yann E. MORIN wrote:
> > I think this will break graph-depends. The python script will do "make
> > <foo>-show-depends" for each package. Now this will return things such
> > as "xenomai-patch"
>
> No, I don't think so, because _PATCH_DEPENDENCIES contain package names,
> not or internal make targets. And I can prove it:
>
> $ make linux-show-depends
> fbtft host-kmod host-lzop toolchain
>
> where fbtft is a kernel extension.
Yes, sorry, Romain explained to me on IRC where I was wrong.
> Have you even tried it? ;-p
No, I only did a review.
> Well, I don;t mind getting rid of the separate show-{build,patch}-depends
> rules. But your proposal is wrong, since we do not have to get rid of
> the trailing -patch, because it's not in there...
Correct. I believe the show-{build,patch}-depends are not useful,
though.
I'll apply this series.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-05 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 14:25 [Buildroot] [PATCH 0/5 v2] linux: fix using extensions (branch yem/kernel-ext) Yann E. MORIN
2015-03-14 14:25 ` [Buildroot] [PATCH 1/5 v2] package infra: add patch-dependencies Yann E. MORIN
2015-03-24 23:22 ` Romain Naour
2015-04-04 13:47 ` Thomas Petazzoni
2015-04-05 9:16 ` Yann E. MORIN
2015-04-05 9:46 ` Thomas Petazzoni [this message]
2015-04-14 0:17 ` Arnout Vandecappelle
2015-03-14 14:25 ` [Buildroot] [PATCH 2/5 v2] docs/manual: add _PATCH_DEPENDENCIES Yann E. MORIN
2015-03-24 23:22 ` Romain Naour
2015-03-14 14:25 ` [Buildroot] [PATCH 3/5 v2] linux: fix extensions Yann E. MORIN
2015-03-24 23:22 ` Romain Naour
2015-03-14 14:25 ` [Buildroot] [PATCH 4/5 v2] linux: simplify adding new extensions Yann E. MORIN
2015-03-26 21:54 ` Romain Naour
2015-03-14 14:25 ` [Buildroot] [PATCH 5/5 v2] linux: migrate extensions to use the new infrastructure Yann E. MORIN
2015-03-26 21:55 ` Romain Naour
2015-04-09 21:11 ` [Buildroot] [PATCH 0/5 v2] linux: fix using extensions (branch yem/kernel-ext) Thomas Petazzoni
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=20150405114624.1077fb67@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox