On Tue, 2011-10-18 at 10:11 +0200, Michal Marek wrote:
On 18.10.2011 09:50, Michal Marek wrote:
On 17.10.2011 18:34, Jeff Mahoney wrote:
So, for now, you're going to need to produce configs for the hardware you want to target. The good news is that all you'll need to do is create the configs, name the packages, and link to kernel-source. That's how all the other kernels are built now.
Jeff forgot to say that all this lives in the kernel-source.git repository: http://kernel.opensuse.org/git. See the config.conf file and the config/ directory for details. scripts/tar-up.sh generates a kernel-source package that can be uploaded to the bs.
Well, there's another step to get the right package description, but I don't know what it is off the top of my head.
That's rpm/package-descriptions.
Plus, you'll need to add appropriate handling for arm to the %install section of rpm/kernel-binary.spec.in. And once you have a kernel package, you'll need to add arm support to perl-Bootloader.
Michal
Apologies if this sounds too noobish, but I'm new at all this plumbing stuff :) OK so I've cloned the repo as mentioned in the url you provided. I opened up the README and made sure my git has the global options set; installed the git-hooks; copied the .patchtag. That much I easily understand. So as I'm trying to create new kernels am I correct in thinking I need to edit config.conf and add: +arm arm/efikamx How are the files in config/ created? Thanks, Andy -- Andrew Wafaa IRC: FunkyPenguin GPG: 0x3A36312F -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org