Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] File local variables
Date: Mon, 13 Oct 2008 17:30:12 +0200	[thread overview]
Message-ID: <200810131730.14114.zecke@selfish.org> (raw)

Hey guys,

imagine the following situation, I have the following files:
	foo-native_1.2.3.bb
	foo_1.2.2.bb
	foo_1.2.3.bb
	foo.inc

now I'm forced to keep PR,PE inside the .inc file but in most of our cases we 
have the PR inside the final recipe file. This means when doing a change to 
an inc I need to open all other users to bump the right thing.

Have you experienced this as well?

I have wondered if something like:
	PE_${FN} = "0"
	PR_${FN} = "0"

in each separate file and then some Bitbake magic to build the sum from every 
included file?

comments? Am I just too lazy?

	z.



             reply	other threads:[~2008-10-13 16:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 15:30 Holger Freyther [this message]
2008-10-17 11:34 ` [RFC] File local variables Robert Schuster

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=200810131730.14114.zecke@selfish.org \
    --to=zecke@selfish.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox