From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] base-{minimal,voidstrap,system}: unify base packages
Date: Tue, 11 Oct 2022 19:46:16 +0200 [thread overview]
Message-ID: <20221011174616.-op2pFw-pUGO0A0mwtOOOFGSBoz3D15zppigADjOgfE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39814@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
There's a closed pull request on the void-packages repository
[RFC] base-{minimal,voidstrap,system}: unify base packages
https://github.com/void-linux/void-packages/pull/39814
Description:
Unifying the three alternative base packages makes it easier to manage dependencies consistently, and having successively more featureful packages depend on the next more spartan package makes the additional inclusions more obvious.
If there is any real reason not to have a `base-system -> base-voidstrap -> base-minimal` dependency chain, we can still preserve dependency maintainability by defining, *e.g.*,
```sh
_minimal_depends="[...]"
_voidstrap_depends="${_minimal_depends} [...]"
```
in the header.
#### Testing the changes
- I tested the changes in this PR: **NO**
next prev parent reply other threads:[~2022-10-11 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 15:09 [PR PATCH] " ahesford
2022-10-08 15:11 ` ahesford
2022-10-08 15:28 ` classabbyamp
2022-10-10 10:03 ` Duncaen
2022-10-10 10:03 ` Duncaen
2022-10-10 10:11 ` Duncaen
2022-10-10 10:12 ` Duncaen
2022-10-10 14:02 ` classabbyamp
2022-10-10 14:11 ` sgn
2022-10-10 14:28 ` ahesford
2022-10-10 14:47 ` Duncaen
2022-10-11 17:46 ` ahesford [this message]
2022-10-11 17:47 ` ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221011174616.-op2pFw-pUGO0A0mwtOOOFGSBoz3D15zppigADjOgfE@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).