Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Raspaudio : how to use buildroot as a git submodule
Date: Wed, 1 Oct 2014 16:08:32 +0200 (CEST)	[thread overview]
Message-ID: <1280276802.26043432.1412172512257.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <1723661717.26039623.1412168336757.JavaMail.root@openwide.fr>



Looking into it a bit deeper, I have a couple of questions for you..

in your current layout 

* BR2_EXTERNAL is shared, so Config.in is shared and external.mk 
is shared
* each project has its own overlay
* each project has its own local.mk
* each project has its own patch subdirectory...
* dl is shared

so I need to understand your use-case a little more. 
As I said my use case is "same project, but different hardware" so
my favorite layout would be

* shared BR2_EXTERNAL
* shared overlay
* shared patches
* different config files
* don't care about local.mk, might as well make it different

This layout makes more sense to me (shared overlay and shared patches)
but I want to make sure it fits your use-case before I do the change

It makes little sense to me to have completely different projects
which are just sharing dl/ since dl is not saved in git and it's
more handy to have completely separate git repo in this case...


If you can tell me a little more, I'll see how I adapt this...

  reply	other threads:[~2014-10-01 14:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1436673405.11266711.1394440215222.JavaMail.root@openwide.fr>
2014-03-10  9:00 ` [Buildroot] Raspaudio : how to use buildroot as a git submodule Jeremy Rosen
2014-03-10 15:30   ` Alvaro Gamez
2014-03-10 15:38     ` Jeremy Rosen
2014-09-26  9:00       ` Alvaro Gamez
2014-09-26 11:56         ` Jeremy Rosen
2014-10-01  9:11           ` Alvaro Gamez
2014-10-01 12:58             ` Jeremy Rosen
2014-10-01 14:08               ` Jeremy Rosen [this message]
2014-10-01 14:18                 ` Alvaro Gamez
2014-10-01 14:37                   ` Jeremy Rosen
2014-10-02  9:53                     ` Alvaro Gamez
2014-10-02 10:10                       ` Jeremy Rosen
2014-10-03  8:03                         ` Jeremy Rosen
2014-10-08  8:19                           ` Alvaro Gamez
2014-10-08 10:11                             ` Jeremy Rosen
2014-10-15 17:42                               ` Arnout Vandecappelle
2014-10-16  8:18                                 ` Jeremy Rosen

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=1280276802.26043432.1412172512257.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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