Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Project layout : where to put the .config files
Date: Thu, 30 Jan 2014 05:39:48 -0600	[thread overview]
Message-ID: <20140130053948.48587221@core2quad.morethan.org> (raw)
In-Reply-To: <153768653.4890423.1391075638245.JavaMail.root@openwide.fr>

On Thu, 30 Jan 2014 10:53:58 +0100 (CET)
Jeremy Rosen <jeremy.rosen@openwide.fr> wrote:

> Buildroot is currently in the process of cleanly separating files
> that are generated by buildroot and are throwaway files (in the 
> output directory) from files that are configuration files (the
> BR2_EXTERNAL directory) 
>

Are you sure of that?

The discussion that I have seen here is that BR2_EXTERNAL tree
is for the "proprietary" files, not just configuration files.

Note: 
Here "proprietary" is used as a generalization for the
portion of the overall build tree that is not required to be
made public.

And:
This list has already had the discussion over how the .config
files should be considered.
I.E: Are they some of the "required public" files to meet the
requirements of Section 3 of the GPLv2 license.

Mike

  parent reply	other threads:[~2014-01-30 11:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1357102119.4889305.1391074415327.JavaMail.root@openwide.fr>
2014-01-30  9:53 ` [Buildroot] Project layout : where to put the .config files Jeremy Rosen
2014-01-30  9:59   ` Thomas De Schampheleire
2014-01-30 10:42     ` Jeremy Rosen
2014-01-30 11:00       ` Thomas De Schampheleire
2014-01-30 11:11     ` Sagaert Johan
2014-01-30 11:39   ` Mike Zick [this message]
2014-01-30 12:34     ` Jeremy Rosen
2014-01-30 13:54       ` Mike Zick
2014-01-30 14:10         ` Jeremy Rosen
2014-01-30 14:42           ` Mike Zick

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=20140130053948.48587221@core2quad.morethan.org \
    --to=minimod@morethan.org \
    --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