X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mail-wm0-f68.google.com (mail-wm0-f68.google.com [74.125.82.68]) by lists.alpinelinux.org (Postfix) with ESMTP id 388525C4DE3 for ; Tue, 23 Jan 2018 19:34:58 +0000 (GMT) Received: by mail-wm0-f68.google.com with SMTP id 141so4104131wme.3 for ; Tue, 23 Jan 2018 11:34:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=UtQWnkbMA+gWaWF3fDaydNiN4vykhaAU8/fm3I2lG20=; b=H+Tv10nqKEFZyT+jdlFVO3hQXNewaPvb+2oxGpHr0kAR0TMxbtak1bC8rKhCYLWGc/ A2V93sJJu9x4CyKSKvVI6Nfa1OMqlEqSdAHurb4KV7TuHrnGI73o3L+2iCIlKmR6du3i SmxJy5S1RZ19kGPDOfiUyqXUHNmpStK/2Gyww+bNX23jqzUUthXoPCzplljVrA25pblC TavaCKvqGeqDZ2/pOyOoSR1iMoUTMKF5Pm2NQ7Jvy+LzAzxwef46/MrkfzALRv1r9jj4 bcV/TM/g4HdhSuiqClSVMt7ttW/6MW9AEzxFot6XIOpda2WgAZXMyC/NQCaMBHLYpmqs f8yg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=UtQWnkbMA+gWaWF3fDaydNiN4vykhaAU8/fm3I2lG20=; b=hof3Op/6u6FLm8shTk4TeA4Y6iboGI4KybgcIIivQ6t5inzuQZj9dQ5btjDHJ1V4Jq piztOWOD8iZKAYVpWnDR81ifExVyxcCOiDLClc2FWSGMaCRJceu9axiJ4OD7tLw4zW8d q51or3PPT3DvBqCz9Noqw8O8SZm7Ehe7mh3DX7bg+HsBeHFbwkm4y1HzZ8xgN11XdtKN cXTbtvDEV3HOyHPR9xrTeZXr3vV5u4msh9na/6dqu6GPFOYO2LC5cATXPH29/F59tbwL kiPKcP6ISG6owYeM5d4vq60dDEj6jDnVUUCh4bwTqx0WQ0iwsXEmGdt97euj7xwkXF31 j4IA== X-Gm-Message-State: AKwxyteFrOcy38NjOmxBFShxlukVJdRvDaQLmcZtbdT5jUmXew6NelWR GvH3ctyLfRuVO+AEoCDGDhMEXAliN4lm9ZDA6LE= X-Google-Smtp-Source: AH8x226wxjOs5E1TW4kHsbihCc9S3sorVaF6ZhokcZysgLPMLIJwFF0vB7N60hZLtGkmsoQac3bAdT0ysRqmF2LfbIQ= X-Received: by 10.28.35.200 with SMTP id j191mr3126127wmj.146.1516736096482; Tue, 23 Jan 2018 11:34:56 -0800 (PST) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Received: by 10.223.179.17 with HTTP; Tue, 23 Jan 2018 11:34:35 -0800 (PST) In-Reply-To: <20180123154751.GA10964@crute.us> References: <20180123154751.GA10964@crute.us> From: Martin Galvan Date: Tue, 23 Jan 2018 16:34:35 -0300 Message-ID: Subject: Re: [alpine-devel] APKBUILD for kernel modules To: Mike Crute Cc: alpine-devel@lists.alpinelinux.org Content-Type: text/plain; charset="UTF-8" 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 guaranteed > to be compatible with the kernel it's built against but not necessarily > 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. 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. Now I understand they're designed for distributing binaries. 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? --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---