Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] fs: add rootfs dependencies to PACKAGES
Date: Sat, 18 Apr 2015 14:35:11 +0200	[thread overview]
Message-ID: <20150418143511.6da17b4d@free-electrons.com> (raw)
In-Reply-To: <55313B9C.3000008@mind.be>

Arnout,

On Fri, 17 Apr 2015 18:58:04 +0200, Arnout Vandecappelle wrote:

>  For dependencies, yes. But the legal-info of package foo really has nothing to
> do with the legal-info of host package bar even if foo depends on bar. IMHO of
> course.

Well, it's very subjective :)

>  But what I really mean is that something like this for external-deps would be
> quite simpler:
> 
> external-deps:
> 	echo $(foreach pkg,$(PACKAGES),$($(pkg)_ALL_DOWNLOADS)))

Yes, it would indeed be shorter in code, and faster in execution.

> > However, one down side of not including all .mk files is that you will
> > no longer be able to do 'make <pkg>-<something>' for a package that
> > isn't enabled. And it is something I do everyday when doing BR
> > development, especially 'make <pkg>-extract' and 'make <pkg>-patch',
> > because that the easiest way to quickly get the source code of a given
> > package extracted somewhere. And I can do this without having to go in
> > menuconfig enable the package.
> 
>  I do that as well, but we could add a make variable to read all .mk files.
> Which was also one of the feedbacks on your patch series IIRC.

That's indeed a possibility.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-04-18 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14  8:17 [Buildroot] [git commit] fs: add rootfs dependencies to PACKAGES Thomas Petazzoni
2015-04-14 10:50 ` Arnout Vandecappelle
2015-04-14 11:54   ` Thomas Petazzoni
2015-04-14 19:08     ` Arnout Vandecappelle
2015-04-14 21:46       ` Yann E. MORIN
2015-04-17 15:36       ` Thomas Petazzoni
2015-04-17 16:09         ` Arnout Vandecappelle
2015-04-17 16:46           ` Thomas Petazzoni
2015-04-17 16:58             ` Arnout Vandecappelle
2015-04-18 12:35               ` Thomas Petazzoni [this message]
2015-04-20 20:10         ` Peter Korsgaard

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=20150418143511.6da17b4d@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