From: hippi777 <hippi777@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] base-system: add nano to dependencies.
Date: Sat, 26 Sep 2020 21:02:52 +0200 [thread overview]
Message-ID: <20200926190252.MreX7jTQ3Myrwlv4Nkwef5XhUH0t5lMaxyNJAXtPlBw@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: 1204 bytes --]
New comment by hippi777 on void-packages repository
https://github.com/void-linux/void-packages/pull/25120#issuecomment-699533065
Comment:
hi there! :)
i like the idea, but i would make both nano and nvi opinionated in this case. also, putting them next to each other would be a bit better imho :D
edit:
maybe opinions arent even necessary as i know that its possible to blacklist packages that others would depend on, but i have no experience with that...
excluding both would give some ppl some inconvenient surprises, so thats not a good solution, while including only nano would make its fans sad, and i think most of the decision makers here would vote on nvi if they cant coexist...
i believe user experience is superior in this case over squeezing out some extra bits of space, and those who prefer the latter should go much further than this to actually achieve something worthy, and that path would already require leaving behind the comfortable defaults, while i think that including nano isnt that much of a big violation against the name, Void :D
(sorry for the long case-study, i think this may be a sensitive and divisive topic, so ive felt like it can be necessary :D )
next prev parent reply other threads:[~2020-09-26 19:02 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 [this message]
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 ` [PR PATCH] [Closed]: " ericonr
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=20200926190252.MreX7jTQ3Myrwlv4Nkwef5XhUH0t5lMaxyNJAXtPlBw@z \
--to=hippi777@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).