From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Custom kernel build - best way to generate a package
Date: Thu, 25 Jan 2018 09:50:14 +0100 [thread overview]
Message-ID: <5e24fe4d-7592-45b4-daa4-690d6fc6823e@siemens.com> (raw)
Hi all,
as indicated before, I'm looking into providing a framework for isar to
help users with building their own kernel packages from un-debianized
kernel sources. I'm now scratching my head how to do that best. Options
I'Ve found so far:
1. make bindeb-pkg (from upstream kernel)
Downside: currently requires patches to feed in missing runtime
dependencies of the generated package. Also, it seems this is not
designed to create full replacements of the standard debian kernel
packages. Might be an uphill battle on the long run.
2. Provide debian/ folder in isar so that dpkg_runbuild works
Question is here where to pick up the debian/ folder from. The
original debian kernel package? The version that Frank once create as
demo [1] (BTW, how was it created?)?
3. make-kpkg
Still unclear to me what pros and cons are here.
Any comments / suggestions would be highly appreciated!
Thanks,
Jan
[1]
https://github.com/ilbers/linux/commit/b7ab449238b8e59943849a10c95d578aa01d70e7
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next reply other threads:[~2018-01-25 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 8:50 Jan Kiszka [this message]
2018-01-25 12:56 ` Jan Kiszka
[not found] ` <5a6c68c4-6062-21f7-f80c-0721c21bb8b8@googlemail.com>
2018-01-25 18:36 ` Jan Kiszka
2018-01-25 19:33 ` Benedikt Niedermayr
2018-01-29 18:46 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e24fe4d-7592-45b4-daa4-690d6fc6823e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox