From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: [RFC] base-system: add nano to dependencies.
Date: Wed, 03 Feb 2021 05:56:11 +0100 [thread overview]
Message-ID: <20210203045611.uEYaI1XW3BD9rrQksZJtcX0yna3-z3IipcNI_slJAgw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25120@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
There's a closed pull request on the void-packages repository
[RFC] base-system: add nano to dependencies.
https://github.com/void-linux/void-packages/pull/25120
Description:
`base-system` already depends on `libmagic` and `ncurses-libs`, which means this only costs the 500K of the `nano` package, which installed is 2M.
It makes for a better user experience nearly for free, since there are often times when one needs to change file contents before they can even connect to the internet and install another editor (edit `/etc/resolv.conf` manually or some weird wireless setup). `nano` is easier to use and way simpler for someone who isn't used to command line stuff, and there are also users who simply prefer it over modal editing. Adding it here instead of as one of the packages used to build live systems makes sense because someone performing a netinstall would be caught by surprise after their netinstall resulted in a system without nano.
prev parent reply other threads:[~2021-02-03 4:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 18:37 [PR PATCH] " ericonr
2020-09-26 18:43 ` hippi777
2020-09-26 19:02 ` hippi777
2020-09-26 19:18 ` mobinmob
2020-09-26 19:21 ` mobinmob
2020-09-26 19:42 ` Anachron
2020-09-26 20:05 ` mobinmob
2020-09-26 20:24 ` ericonr
2020-09-26 20:24 ` ericonr
2020-09-26 20:30 ` hippi777
2020-09-26 22:49 ` q66
2020-09-26 22:50 ` q66
2020-10-30 22:46 ` ofiala-a51
2020-10-30 22:48 ` ofiala-a51
2020-10-30 22:48 ` ofiala-a51
2020-10-30 23:04 ` pullmoll
2020-10-31 15:41 ` ericonr
2020-12-30 7:09 ` the-maldridge
2021-02-03 4:56 ` ericonr
2021-02-03 4:56 ` ericonr [this message]
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=20210203045611.uEYaI1XW3BD9rrQksZJtcX0yna3-z3IipcNI_slJAgw@z \
--to=ericonr@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).