From: Leo Famulari <leo@famulari.name>
To: 47852@debbugs.gnu.org
Cc: olv345@hotmail.com, raghavgururajan@disroot.org,
rprior@protonmail.com, public@yoctocell.xyz, hello@elenq.tech,
rg@raghavgururajan.name, jackhill@jackhill.us
Subject: [bug#47852] [PATCH] gnu: Add sc-im
Date: Tue, 20 Apr 2021 00:57:56 -0400 [thread overview]
Message-ID: <YH5fVE6p34ebHHDa@jasmine.lan> (raw)
In-Reply-To: <5c38f2307986364b38c2eab481e4088b@dismail.de>
On Mon, Apr 19, 2021 at 04:46:10PM +0000, jgart via Guix-patches via wrote:
> Yes, I think it would be better if we did this in a new issue.
>
> Ryan Prior suggested tui-apps as a new module name.
>
> I like that!
>
> sc-im, visidata, newsboat, and calcurse fit that bill. There's probably others that can go in there.
I think we should avoid moving packages around unless there is a
compelling reason to do it.
There are a few reasons not to move packages. It makes the Git history
harder to use (`git log` and `git blame`), it can make Git merges of
long-running branches trickier, and it can break 3rd party channels. And
sometimes it's annoyingly hard work to properly move or duplicate the
copyright attributions to the new file.
In general, the location of the packages is not something that users see
or care about, but it does matter for developers. To me, the conceptual
satisfaction of a nicely defined category does not justify the headaches
that can result from moving packages around.
next prev parent reply other threads:[~2021-04-20 4:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 21:52 [bug#47852] [PATCH] gnu: Add sc-im jgart via Guix-patches via
2021-04-17 22:22 ` ElenQ Technology
2021-04-17 23:29 ` Jack Hill
2021-04-17 23:54 ` jgart via Guix-patches via
2021-04-18 0:32 ` jgart via Guix-patches via
2021-04-18 9:25 ` Xinglu Chen
2021-04-18 15:39 ` jgart via Guix-patches via
2021-04-18 16:40 ` Xinglu Chen
2021-04-18 16:57 ` jgart via Guix-patches via
2021-04-19 15:33 ` Xinglu Chen
2021-04-19 16:46 ` jgart via Guix-patches via
2021-04-19 21:48 ` Ekaitz Zarraga
2021-04-20 4:57 ` Leo Famulari [this message]
2021-04-22 19:56 ` jgart via Guix-patches via
2021-04-23 9:22 ` jgart via Guix-patches via
2021-04-23 16:41 ` Leo Famulari
2021-04-20 5:00 ` Leo Famulari
2021-11-19 1:22 ` [bug#47852] [PATCH 1/2 v6] " jgart via Guix-patches via
2021-11-19 1:22 ` [bug#47852] [PATCH 2/2] gnu: Move visidata to (gnu packages spreadsheet-apps) jgart via Guix-patches via
2021-11-22 21:20 ` [bug#47852] [PATCH 1/2 v6] gnu: Add sc-im Leo Famulari
2021-11-22 23:23 ` jgart via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YH5fVE6p34ebHHDa@jasmine.lan \
--to=leo@famulari.name \
--cc=47852@debbugs.gnu.org \
--cc=hello@elenq.tech \
--cc=jackhill@jackhill.us \
--cc=olv345@hotmail.com \
--cc=public@yoctocell.xyz \
--cc=raghavgururajan@disroot.org \
--cc=rg@raghavgururajan.name \
--cc=rprior@protonmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).