X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail.wilcox-tech.com (mail.wilcox-tech.com [45.32.83.9]) by lists.alpinelinux.org (Postfix) with ESMTP id 527975C4E13 for ; Tue, 23 Jan 2018 23:36:33 +0000 (GMT) Received: (qmail 18368 invoked from network); 23 Jan 2018 23:36:30 -0000 Received: from 107-131-85-28.lightspeed.tulsok.sbcglobal.net (HELO ?192.168.1.237?) (awilcox@wilcox-tech.com@107.131.85.28) by mail.wilcox-tech.com with ESMTPA; 23 Jan 2018 23:36:30 -0000 Subject: Re: [alpine-devel] APKBUILD for kernel modules To: alpine-devel@lists.alpinelinux.org References: <20180123154751.GA10964@crute.us> From: "A. Wilcox" Organization: =?UTF-8?Q?Ad=c3=a9lie_Linux?= Message-ID: Date: Tue, 23 Jan 2018 17:36:33 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="epiMuEBW3wTBIUgcSaR2mGSMk89mXLVER" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --epiMuEBW3wTBIUgcSaR2mGSMk89mXLVER Content-Type: multipart/mixed; boundary="hUsbrAs9jImhqA7fLsa5qrea5QcOlsQ39"; protected-headers="v1" From: "A. Wilcox" To: alpine-devel@lists.alpinelinux.org Message-ID: Subject: Re: [alpine-devel] APKBUILD for kernel modules References: <20180123154751.GA10964@crute.us> In-Reply-To: --hUsbrAs9jImhqA7fLsa5qrea5QcOlsQ39 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 01/23/18 13:34, Martin Galvan wrote: > 2018-01-23 12:47 GMT-03:00 Mike Crute : >> I built a kernel module package recently and there really aren't a lot= >> of good docs for this. As I understood the rationale for co-versioning= >> modules with the kernel it's about compatibility. A module is guarante= ed >> to be compatible with the kernel it's built against but not necessaril= y >> against newer or older kernels, thus it doesn't make sense for the >> module to maintain it's own version but rather to adopt the version of= >> the kernel it's built for. >=20 > I understand. I thought a APK package would do something for me like > packages generated by dkms-mkdeb do: give the module sources to the > user, then rebuild the module in the target system for its running > kernel. If only. > What it's not fully clear to me is how the module binaries are > distributed. What if a user with an older kernel updates their aports > tree, then tries to apk add a module package? How does the apk > machinery know which binaries to provide? I'm planning on fixing APK to handle kernel stuff better, because it's pretty terrible right now; you can really wedge a system bad if you upgrade the kernel package unknowingly (via `apk upgrade -qa` or such) and then add a module package. Best, --arw --=20 A. Wilcox (awilfox) Project Lead, Ad=C3=A9lie Linux http://adelielinux.org --hUsbrAs9jImhqA7fLsa5qrea5QcOlsQ39-- --epiMuEBW3wTBIUgcSaR2mGSMk89mXLVER Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJMBAEBCAA2FiEEjNyWOYPU1SaTSMHHyynLUZIrnRQFAlpnxwEYHGF3aWxmb3hA YWRlbGllbGludXgub3JnAAoJEMspy1GSK50Uz5kP/i0V/Bw5O/QLiqx8cpgps1dg Mj5agIYv4iNUS7zJydISNWjgJFqgOJFI0ZQqn//zeGmKrAe1Cnc3Hg9CbDg6cbbP EveXNz68hgqi7SHl+cs0lPs6VIQ37FluPzlY/QaROWcgFaEEH1bQJVX49lwJCMK4 JXcRDwIB6wJ2J6RRTxPfvJWzTSF3nkxCYiRfD8sqRNy2kurYsl6I3mZ9lc3KVSiJ +SvZshOZAxcPeY24PU5YbVnFJqXEB/SGZtDh/85rDtCfxKwO3eAGCeuN8HQBJ9S7 s0AoZW+QBzxi1lamt51NYHVyZDiJ5xAS17IZRjXC/R3EydIuQU0TJ8jLSp8e9Wkl 82JYQT7xebEfIFqreQvXdQfW7CnaTAGjJebc84CnodZ8SNzrhK6LVQkGkGxIsg+d M2xXHKi2nL3f/fxznyKJZExGMU8lQDGFsP2YJldGLLGBZz6JHxs/b2kRxBQO5EIt 2HaueZ1AqXLmVnja27srbFoc9WnwZkGsnaUX0W6Z+lmBXP2QohhNBFClXPsCNh/y sYBHTeTogpCmn7D+K16uaI+wsFYDDsYDrEswm8el2pwK1taS8HX50eyN0GW3Ef3w v3wglfJGnJgJ2TaQHvUEm7HKmaIgGI3Oxg6KdazeKvzav3GS/H8keC28EDsnxF1c yMgdspO2YS3bG7UoG1Ql =2oC+ -----END PGP SIGNATURE----- --epiMuEBW3wTBIUgcSaR2mGSMk89mXLVER-- --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---