Re: [RFC] How to handle external kernel patches in oe the right way?

[Koen Kooi <k.kooi@student.utwente.nl>]

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

Dr. Michael Lauer schreef:
> Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
> 
>> Richard Purdie schreef:
>>> On Tue, 2007-09-04 at 22:29 +0200, Stefan Schmidt wrote:
>>>> Due to my work on OpenEZX (http://www.openezx.org) I'm in touch with
>>>> external kernel patches used in OE to build working kernels for
>>>> different Motorola mobile phones.
>>>>
>>>> Talking with Koen about the best way to handle this we have some
>>>> slightly different opinions on this. So we like to get some more
>>>> opinions on this before pinning to a strategy.
>>>>
>>>> Koen like to pull the patches from a known-good rev into oe to have
>>>> them all at one place for less fragile building and tweaking.
>>>>
>>>> I prefer OE to use our svn server with a fixed SRCREV which gets
>>>> updated once a newer version is known good. I'm not a fan of
>>>> duplicating the patches in OE if some small tweaking patches can also
>>>> handle it.
>>> Personally I agree with this in principle, I've never liked maintaining
>>> kernel patches in OE directly either.
> 
>> I'm having issues with crap like do_prepatch. Patches are only applied by patch.bbclass,
>> not some hand written voodoo <period>.
> 
> Very well. If it annoys you so much, feel free to enhance patch.bbclass to
> deal with upstream series files while retaining OE-added patches to it.

Like I said *many* times before, the ezx patch script does that.

> Until then, I think we shouldn't make life more complicated for the
> actual upstream developers just because of going a bit too far wrt. to
> our principles.

How many times to I have to offer to do the work for you!?!?!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG3whDMkyGM64RGpERAliMAJ9JEf0KSB1/nZdLbB/9eKV1zKzpUgCdHvj2
iXImgX7irQZKoeFb5hrfecM=
=/SB3
-----END PGP SIGNATURE-----