Arjan van de Ven wrote: >> +n900: kernel.spec.in series makespec.pl >> + @touch N900; >> + @perl makespec.pl< kernel.spec.in> kernel-n900.spec ; > > why make a separate spec like this? sounds completely unneeded to me.... > for arm it will only build the n900 anyway right now > >> -tmp-arm-config: config-arm-generic config-generic >> - perl merge.pl $^> $@ >> - >> -kernel-n900.config: config-arm-n900 tmp-arm-config >> - perl merge.pl $^> $@ >> +kernel-arm-n900.config: config-arm-n900 >> + cp $^ $@ > > please don't do this and use our hierarchical configuration system > it's very important for meego to have as consistent configurations as > possible.
I'd certainly like to; could you point me at the docs/README for the various scripts in that package? Essentially if I have a working .config file for a kernel for my new device how do I package it? Clearly there's a kernel.spec.in with the magical spec.in @@M macros but your comment above suggests that that shouldn't be used in the way I'd assumed? We have: * configcommon.pl * makespec.pl * merge.pl * Makefile.config I notice there's a config-generic. What is this supposed to be for? I'd expect it to contain the policy level kernel decisions like yes/no for process accounting, ipv6, netlink, security etc. David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
