Received: from shout02.mail.de (shout02.mail.de [62.201.172.25])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id BBB4C780DB5
	for <~alpine/users@lists.alpinelinux.org>; Thu, 10 Feb 2022 14:20:09 +0000 (UTC)
Received: from postfix01.mail.de (postfix01.bt.mail.de [10.0.121.125])
	by shout02.mail.de (Postfix) with ESMTP id 619BBA139E
	for <~alpine/users@lists.alpinelinux.org>; Thu, 10 Feb 2022 15:20:09 +0100 (CET)
Received: from smtp03.mail.de (smtp03.bt.mail.de [10.0.121.213])
	by postfix01.mail.de (Postfix) with ESMTP id 475298014F
	for <~alpine/users@lists.alpinelinux.org>; Thu, 10 Feb 2022 15:20:09 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.de;
	s=mailde202009; t=1644502809;
	bh=oWRhp7yKL4ZNzTGR/ZcqzWYhk4Oq6K+ASMV4oca+kTg=;
	h=From:Subject:Message-Id:Date:To:From:To:CC:Subject:Reply-To;
	b=gaApes330NH88K8XJs3bU8s7oGPxZLco9CnqizLEAtPKqulZiPlKCWeIZrrlj2WJy
	 lfDK5X1WW4PLmRh1kBOj21TNnUhIFx9CN2ts2eXDM5QkwYAnfHddwi125y238X2n79
	 eoOzNlXGBsZDNuzshdWwPSUUTElEnOokNv0DLKq2yr/YBZKObzeqmP7rKF5VPzPlpE
	 vr2EIzPM0oRYmLpaZH4x7b82qy9DeC1I3fYrJscbURBFmMLDyH4iiaTvcMPwSGdr1j
	 P1cG1kb6HzWAIIJWyHZnzbUodph0Wr/q5XykskhWp47NbuI9LvA0KjXgO/GZ4/ucvu
	 yXTZrbxKI0FcA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=top-email.net;
	s=top-email201307; t=1644502809;
	bh=oWRhp7yKL4ZNzTGR/ZcqzWYhk4Oq6K+ASMV4oca+kTg=;
	h=From:Subject:Message-Id:Date:To:From:To:CC:Subject:Reply-To;
	b=icaAGuCe/wtnj7HgK4U2ShqxzSwM8ZPFXnFZhldJWl7BGW3fsMWRdhBJi3DTgdZMn
	 OR0s4OT3mQnigkhoQBvv2m93m86nUB2CChAZA8j6I2tQ6tKgOLtzei7G8CKGH2Q6Ap
	 YLpdPGfZSH7C74kjrTfUUrL9h2RYMjYPoGN7heUk=
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by smtp03.mail.de (Postfix) with ESMTPSA id 09751A0096
	for <~alpine/users@lists.alpinelinux.org>; Thu, 10 Feb 2022 15:20:07 +0100 (CET)
From: Me irc-ing just this minute <ircing.wu39@top-email.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Package composition by Alpine Linux
Message-Id: <A15A02DB-7B37-40B5-8B0E-CB49DA902237@top-email.net>
Date: Thu, 10 Feb 2022 15:20:06 +0100
To: ~alpine/users@lists.alpinelinux.org
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
X-purgate-size: 1169
X-purgate-ID: 154282::1644502809-00004C55-843E48F0/0/0

Hi,
We were kindly provided (by some external community)
with suggestion to reach out Alpine Linux to look for
solution regarding our goals.

Q: Does Alpine package management yet distribution installer
refrain from elevating dependencies of every single package
to mandatory one while neither underlying hardware
nor Alpine setup user asks for functionalities provided by packages
elevated to mandatory?

The intention is to have in used setup package composition as lean
as possible. Lot of Linux distributions we could deal with so far
have the bad habit to elevate lot of unused staff to mandatory =
dependencies.
Neither underlying hardware has capabilities to support
addressed functionality nor user is asking for such.

This is big issue from system and user data integration point of view.

Alpine lead axiom =E2=80=9CSmall. Simple. Secure" raises=20
the hope property pointed out above could be fulfilled here.

If by any way user finds some mandatory dependency
which in reality is to be classified as redundant one
(based on criteria mentioned above)
how easily is for user/administrator to get rid of it?

Best Regards
wu 39=