X-Original-To: alpine-devel@lists.alpinelinux.org Received: from sender-pp-092.zoho.com (sender-pp-092.zoho.com [135.84.80.237]) by lists.alpinelinux.org (Postfix) with ESMTP id 54B205C4EAA for ; Mon, 12 Feb 2018 09:19:34 +0000 (GMT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:message-id:in-reply-to:subject:mime-version:content-type:user-agent; b=W/JlS5Kba3KfL36qNj1muc4w0SopLMZEpLpNQTWrwy7u9xIfa+ZNt+ME5svhalx52RsBArejgZZD M6xFad3XbldEj+7kAQfEBFGEcvLwloVK4bTgAVuug5mvypFgCqpu Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1518427172076634.8709257201364; Mon, 12 Feb 2018 01:19:32 -0800 (PST) Received: from [89.76.36.159] by mail.zoho.com with HTTP;Mon, 12 Feb 2018 01:18:31 -0800 (PST) Date: Mon, 12 Feb 2018 10:19:32 +0100 From: =?UTF-8?Q?Przemys=C5=82aw_Pawe=C5=82czyk?= To: "alpine-devel" Message-ID: <161894efe87.111ebc5a251296.390323127337732549@zoho.com> In-Reply-To: Subject: [alpine-devel] RFC: Introducing tools-base meta package 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="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: Medium User-Agent: Zoho Mail X-Mailer: Zoho Mail Hi, Alpiners! What would you say about introducing new meta packages: - tools-base - depending on busybox for now, - tools-base-initscripts - depending on busybox-initscripts for now? After introducing they could replace busybox and busybox-initscripts as dependencies of alpine-base. (Maybe provides="/bin/sh" should be moved from busybox to tools-base then, not sure yet.) It will greatly ease possible future changes like replacing busybox or parts of it, even if such changes won't be happening soon, i.e. before releasing Alpine Linux 3.8. --- Mind that this RFC is not about replacing busybox, but about introducing changes that would make such endeavour more pain-free if ever happening. But let me very briefly go into that territory too. Why replace busybox? To have better implementation of widely used tools, of course. Any candidates? 2 examples come to my mind right now. - toybox It "combines common Linux command line utilities together into a single BSD-licensed executable that's simple, small, fast, reasonably standards-compliant". It's not as complete as busybox, so no drop-in replacement yet, but it has many toys already available: http://landley.net/toybox/status.html Replacing busybox partially would require reorganizing its package, and most likely switching from trigger-based symlinks to explicit ones provided by some subpackages. - mawk It's "an interpreter for the AWK Programming Language". It will possibly allow to make some packages depend on it instead of gawk. I believe A. Wilcox can share details why it's better than busybox's awk, after dealing with it in Adelie Linux. Regards, Przemek --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---