X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx0.jmt.gr (mx0.jmt.gr [81.7.7.41]) by lists.alpinelinux.org (Postfix) with ESMTP id C00C25C4A56 for ; Sun, 6 Nov 2016 14:56:19 +0000 (GMT) Received: from webmail.jmt.gr (web3.jmt.gr [IPv6:2a02:180:a:62:1::443]) by mx0.jmt.gr (Postfix) with ESMTPSA id D876480C40 for ; Sun, 6 Nov 2016 14:56:17 +0000 (GMT) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sun, 06 Nov 2016 14:56:17 +0000 From: Johannes Matheis To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] Packaging WireGuard (kernel module + virtual package) Message-ID: X-Sender: jomat+alpinedevellist@jmt.gr User-Agent: Roundcube Webmail/1.1.2 Hello, I'm about to package WireGuard[0] for Alpine Linux. My work-in-progress is currently in my github repo[1]. The current state is: - wireguard.ko is built for grsec and subpackaged to 'wireguard-kmod' - management tools are subpackaged to 'wireguard-tools' - package 'wireguard' is empty but depends on the other two - a wireguard-doc package is also availabe Arising questions are: - is there a recommended way for packaging kernel modules esp. how to handle the different kernel flavors. e. g. sch-cake or drbd9 are only available for grsec - is it correct to build the purely virtual package 'wireguard' like this? abuild complains about its architecture. Any other feedback, ideas, pull requests are welcome, too :-) Bye, jomat [0] https://wireguard.io [1] https://github.com/jomat/aports/tree/master/community/wireguard --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---