reduce the monkey work: BPN/BP available

[Robert Schuster <thebohemian@gmx.net>]

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

Hi,
I just pushed the patches that adds the BP (base package) and BPN (base
package name) variables.

They are there to reduce the amount of 'monkey work' needed for a
-native recipe that has a corresponding (and very similar) non-native
recipe.

I plan to add this to the manual soon but describe it here so you can
use before it ends up there.

The problem with -native (also for -initial, -cross and -intermediate
suffix) recipes ist that they do not work correctly in regard to
SRC_URI, S and FILESPATH when those make use of P or PN.

Current workaround is to use the literal package name instead of the
variable and/or redefine some variables in the -native recipe. The
latter is what Koen called the 'monkey work'.

For future recipes you should consider using BP when you want a P that
does not change in recipes ending with -native, -initial, -cross or
-intermediate (more suffixes can be supported if needed, look at
base.bbclass).

I also added the neccessary things to make dealing with patches that
should be applied to both the non-native and the native recipe easier.
The search path includes BPN and then BP. I added them after the entries
for P and PN.

So for a recipe called foo-native_7.33.bb patches will be searched in
this order automatically:
./foo-native-7.33
./foo-native
./foo-7.33
./foo
(and the others like ./files and whatnot)

The BP/BPN stuff does not affect existing recipes since they do not use
those variables. Obviously it would be nice to simplify them when a new
package version is added or such.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]