From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] File local variables
Date: Fri, 17 Oct 2008 13:34:36 +0200 [thread overview]
Message-ID: <48F8784C.9010907@gmx.net> (raw)
In-Reply-To: <200810131730.14114.zecke@selfish.org>
[-- Attachment #1: Type: text/plain, Size: 790 bytes --]
Hi,
Holger Freyther schrieb:
> 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.
Clear to this point.
> Have you experienced this as well?
Sure. :)
> I have wondered if something like:
> PE_${FN} = "0"
> PR_${FN} = "0"
What is ${FN}?
> in each separate file and then some Bitbake magic to build the sum from every
> included file?
>
> comments? Am I just too lazy?
Can you explain a bit how this is being supposed to being used.
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2008-10-17 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 15:30 [RFC] File local variables Holger Freyther
2008-10-17 11:34 ` Robert Schuster [this message]
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=48F8784C.9010907@gmx.net \
--to=thebohemian@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox