[oe] [meta-systemd][PATCH] connman: Rename .bbappend to match new version from oe-core

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Jansa schreef op 29-01-14 11:15:
> On Wed, Jan 29, 2014 at 08:55:50AM +0100, Koen Kooi wrote: Martin Jansa
> schreef op 28-01-14 22:18:
>>>> Signed-off-by: Martin Jansa <Martin.Jansa at gmail.com> --- 
>>>> .../connman/{connman_1.20.bbappend => connman_%.bbappend} | 0 1
>>>> file changed, 0 insertions(+), 0 deletions(-) rename 
>>>> meta-systemd/oe-core/recipes-connectivity/connman/{connman_1.20.bbappend
>>>>
>>>> 
=> connman_%.bbappend} (100%)
>>>> 
>>>> diff --git 
>>>> a/meta-systemd/oe-core/recipes-connectivity/connman/connman_1.20.bbappend
>>>>
>>>> 
b/meta-systemd/oe-core/recipes-connectivity/connman/connman_%.bbappend
>>>> similarity index 100% rename from 
>>>> meta-systemd/oe-core/recipes-connectivity/connman/connman_1.20.bbappend
>>>>  rename to 
>>>> meta-systemd/oe-core/recipes-connectivity/connman/connman_%.bbappend
>
>>>> 
> Can we come up with a plan to drop these packaging bbappends? We've
> already had more than one OE (well yoctoproject) release so distros have
> had ample time to adjust to the new packaging system.
> 
>> I have already updated SHR as distro, but that doesn't fix
>> upgrade-path on target (for crazy folks who would try to opkg upgrade
>> themselves from dylan to master).

I think we need to be pragmatic here, dylan -> master won't work when using
opkg (haven't tried RPM), so I'd like to get rid of bbappends that are
present purely for historical reasons.
I'm sure someone can come up with a image recipe in dylan where upgrade to
master does work, but it breaks for the commonly used angstrom images.

So after 'dizzy' (or whatever RP will call it) can we drop these bbappends?

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFS6NrmMkyGM64RGpERAtf+AJ4wQeFFJUPngxOudYONWaKcH2kF2QCfclab
MDqmkEQ+AWT9bmozHspawxE=
=eQfD
-----END PGP SIGNATURE-----