all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Tai <atai@atai.org>
To: 宋文武 <iyzsong@envs.net>
Cc: 59059@debbugs.gnu.org
Subject: [bug#59059] [PATCH] gnu: terminator: Renamed to "gnome-terminator" and update to 2.1.2
Date: Sat, 28 Jan 2023 22:22:38 -0800	[thread overview]
Message-ID: <CAJsg1E_wwuxZ0j6ut4D3c9_=LCSD+Hbm3VHKBxZmYKU7Mmme5A@mail.gmail.com> (raw)
In-Reply-To: <87k015j21a.fsf_-_@envs.net>

Hi, I saw there are other software packages named "terminator" (on Mac
OS, I think) and I am afraid of name collisions.   Also the
maintainers of the terminator package use the term gnome-terminator in
their own documentation ,  website, etc.  I guess it is better to be
specific as this is something in the GNOME ecosystem.

Thanks

On Sat, Jan 28, 2023 at 10:19 PM 宋文武 <iyzsong@envs.net> wrote:
>
> Andy Tai <atai@atai.org> writes:
>
> > * gnu/packages/gnome.scm (gnome-terminator): Rename variable from
> > (terminator):  …this.  Redefine using DEPRECATED-PACKAGE.
> > Update to 2.1.2
>
> Hello, I have commit the 2.1.2 update.
>
> Why rename it to gnome-terminator?  I think terminator is fine, because
> that in ArchLinux the package named so, and its executeble is
> 'terminator' not 'gnome-terminator'.




      reply	other threads:[~2023-01-29  6:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05 19:45 [bug#59059] [PATCH] gnu: terminator: Renamed to "gnome-terminator" and update to 2.1.2 Andy Tai
2022-12-23  6:43 ` [bug#59059] ping Andy Tai
2023-01-11 22:09 ` [bug#59059] [PATCH] gnu: terminator: Renamed to "gnome-terminator" and update to 2.1.2 zimoun
2023-01-13  6:51 ` Andy Tai
2023-01-17 19:59 ` [bug#59059] ping Andy Tai
2023-01-28  9:25 ` [bug#59059] [PATCH v2] gnu: terminator: Renamed to "gnome-terminator" and update to 2.1.2 Andy Tai
2023-01-29  6:19   ` [bug#59059] [PATCH] " 宋文武 via Guix-patches via
2023-01-29  6:22     ` Andy Tai [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='CAJsg1E_wwuxZ0j6ut4D3c9_=LCSD+Hbm3VHKBxZmYKU7Mmme5A@mail.gmail.com' \
    --to=atai@atai.org \
    --cc=59059@debbugs.gnu.org \
    --cc=iyzsong@envs.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.