All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Improve our default conf file setup
Date: Tue, 16 Feb 2010 11:49:47 +0000	[thread overview]
Message-ID: <1266320987.6436.135.camel@rex> (raw)
In-Reply-To: <ac9c93b11002160258m2ddee8absd0510adad4179c6d@mail.gmail.com>

On Tue, 2010-02-16 at 11:58 +0100, Frans Meulenbroeks wrote:
> Sounds quite nice.
> Didn't study the class code, but it would be nice if within layer.conf
> I could use a relative path, which then is turned into an absolute
> path when the layer.conf file is read

This is what the LAYERDIR variable gives us. 

Having relative paths would lose all context outside the layer.conf
file. We could hardcode a list of variables that needed to be processed
and so on but LAYERDIR removes all that complexity whilst still letting
you move things around.

> That means layer.conf can become very standard wrt BBPATH etc. and you
> can even move layers around.

You should be able to do that with my proposal, the only file that would
need changing is bblayers.conf, not the layers themselves.

Cheers,

Richard




  parent reply	other threads:[~2010-02-16 11:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16 10:34 RFC: Improve our default conf file setup Richard Purdie
2010-02-16 10:58 ` Frans Meulenbroeks
2010-02-16 11:00   ` Frans Meulenbroeks
2010-02-16 11:49   ` Richard Purdie [this message]
2010-02-16 14:16     ` Chris Larson
2010-02-16 15:36       ` Richard Purdie
2010-02-18  7:47         ` Frans Meulenbroeks
2010-02-18  9:09         ` Marcin Juszkiewicz
2010-02-18 16:13           ` Chris Larson
2010-02-18 16:58             ` Richard Purdie
2010-02-20  1:39               ` Chris Larson
2010-02-20 22:58                 ` Richard Purdie
2010-02-21  1:19                   ` Chris Larson
2010-02-23 17:55                     ` Richard Purdie
2010-02-23 18:14                       ` Chris Larson
2010-02-16 11:15 ` Marco Cavallini
2010-02-16 11:47   ` Richard Purdie

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=1266320987.6436.135.camel@rex \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.