X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 5A42D5C4ED4 for ; Fri, 16 Jun 2017 08:16:52 +0000 (GMT) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 02D529E220C; Fri, 16 Jun 2017 08:16:52 +0000 (GMT) Received: from ncopa-desktop.copa.dup.pw (15.63.200.37.customer.cdi.no [37.200.63.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: n@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id CA5F39E21FA; Fri, 16 Jun 2017 08:16:50 +0000 (GMT) Date: Fri, 16 Jun 2017 10:16:43 +0200 From: Natanael Copa To: =?ISO-8859-1?B?Q+Fn?= Cc: alpine-devel@lists.alpinelinux.org Subject: Re: [alpine-devel] Alpine features and the future Message-ID: <20170616101643.77795057@ncopa-desktop.copa.dup.pw> In-Reply-To: <20170615200132.GA24181@alpine> References: <20170615200132.GA24181@alpine> X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-alpine-linux-musl) 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=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Thu, 15 Jun 2017 21:01:32 +0100 C=E1g wrote: > Apparently there has been some sort of speculation regarding > replacement of some components of the system with others, and > apparently many moons ago last time, at least on this list. Replacing core components requires a signinficant amount of work. Its not like we have overflow of resources and look for things to spend our time on. So if we replace core components it needs to justify the time spent on it and the risk of break things for users. In other words, we don't replaces components just because we can. > I would like to know Alpine developers' and users' positions on: >=20 > 1. BusyBox. Does it need a replacement such as sbase/ubase, > The Heirloom Toolchest, ToyBox or maybe even 9base or Coreutils? no. > 2. GNU software. Should it be replaced by analogues? For example, > make with bmake, bc with heirloom bc, bison with byacc, ncurses > with NetBSD curses. replacing GNU make is not a goal, specially if it require us to refactor Makefiles of 1000+ packages. we ship both bison and byacc. You are free to use any. ncurses thoug, I wouldn't mind replace GNU ncurses as I have had some issues in the past with it. (Headers got wrong so lots of packages got miscompiled). Before replacing ncurses I want be relatively sure that it will not break things. > 3. gcc/clang Shiz has been working on it and I would not mind replace gcc with clang as default compiler. >=20 > 4. OpenRC. Should Alpine switch to an alternative like runit, s6 > or svc? Should /sbin/init be sinit? openrc sort of does the job, but i'm not 100% happy with it. I like the ideas behind s6 but find it a bit "weird" (due to djb style) and I find it bigger than I'd like. > 5. In case of replacing BusyBox with something that lacks an > editor, what would become the default? nvi, vim, neovim, elvis > traditional vi, nano or vis? Or maybe there will be two like > in OpenBSD or a load as in Slackware? >=20 > 6. What would be the default shell? mksh, pksh or dash? Or maybe > bash? i don't see any reason to replace busybox. -nc >=20 >=20 > Thanks >=20 --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---