diff options
| author | Paul Sokolovsky <pmiscml@gmail.com> | 2006-10-27 01:07:40 +0000 |
|---|---|---|
| committer | Paul Sokolovsky <pmiscml@gmail.com> | 2006-10-27 01:07:40 +0000 |
| commit | 3903dc969a1710e80c49f78adf2f1639956185b4 (patch) | |
| tree | f05878d9299a5ee2e652f13c8b95bf637b83210b /packages/python/python-numarray_1.1.1.bb | |
| parent | 11d174ab5324bd1e46cc86532dbb3aa3c4f2d700 (diff) | |
linux-handhelds-2.6: Prepare to finish upgrade to 2.6.17.
* Aim: support few kernel releases nicely and transparently.
* Issue: different kernel versions/releases (may) have different defconfigs.
* Requirement: we need files dir to be override not just on PN, amd not just on
MACHINE, but additionally on some version string, which doesn't necessarily have
to be PV (for example, current situation is that 2.6.16 vs 2.6.17 need different
defconfigs, while potentially *some* -hh tags may have that need too).
* Solution: I could get per-MACHINE overrides work automagically if FILESPATH is
overriden. So, emulate that with adding both per-version dir (foo) and foo/${MACHINE}
at the same time (and at the right order).
* Rename linux-handhelds-2.6/ to linux-handhelds-2.6-2.6.16/, as it really contains
defconfigs for those kernels. "HEAD" kernel version will still use linux-handhelds-2.6
(i.e. TODO: add 2.6.17 defconfigs to linux-handhelds-2.6/).
Diffstat (limited to 'packages/python/python-numarray_1.1.1.bb')
0 files changed, 0 insertions, 0 deletions