From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: 35586@debbugs.gnu.org
Subject: bug#35586: GNOME
Date: Mon, 06 May 2019 21:20:45 +0200 [thread overview]
Message-ID: <87zhnzfkz6.fsf@nckx> (raw)
In-Reply-To: <c99df64bf65aed4210c059cc2ff5628129be9abc.camel@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 1907 bytes --]
Raghav,
Thanks for taking a look at this. I'm sure there's plenty to be
improved in how we package a large collection of software like
GNOME in an intuitive way.
Raghav Gururajan wrote:
> The following gnome core applications have already been included
> in
> guix's gnome package but requires correct renaming?
>
> epiphany --> gnome-web
Using ‘correct’ here is a bit strong.
~ λ guix install epiphany
~ λ gnome-web
bash: gnome-web: command not found
~ λ epiphany
# browsin' time
While we don't blindly name packages after the binaries they
provide, of course, a look at the project's own publications
doesn't reduce the confusion. Ironic.
“Web is the web browser for the GNOME desktop and for elementary
OS,
based on the popular WebKit engine. It offers a simple, clean,
beautiful view of the web featuring first-class GNOME and
Pantheon
desktop integration. Its code name is Epiphany.
You may install Web from the software repositories of most
Linux
operating systems, where it is normally packaged as
"epiphany-browser" or "epiphany". ”[0]
The README[1] mainly, but not exclusively, talks about ‘Epiphany’.
Even the two URLs balance each other out. I don't think there's
enough here to justify gross renaming, and in the name of all
that's holy let's avoid another mass renaming incident.
Personally, I think adding ‘GNOME Foo’ to the synopses of all
these packages is sufficient (epiphany does this by coincidence,
calling itself the ‘GNOME web browser’). Eventually, this could
be another use for the separate (G)UI display name field as
suggested in the games thread. :-)
Package names aren't opaque identifiers, but they can be a little
technical IMO.
Kind regards,
T G-R
[0]: https://wiki.gnome.org/Apps/Web
[1]: https://github.com/GNOME/epiphany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-06 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 18:20 bug#35586: GNOME Raghav Gururajan
2019-05-05 18:52 ` pelzflorian (Florian Pelz)
2019-05-05 19:23 ` Raghav Gururajan
2019-05-05 20:48 ` pelzflorian (Florian Pelz)
2019-05-05 19:36 ` Raghav Gururajan
2019-05-05 20:50 ` pelzflorian (Florian Pelz)
2019-05-06 7:51 ` Raghav Gururajan
2019-05-06 9:05 ` pelzflorian (Florian Pelz)
2019-05-06 14:02 ` Raghav Gururajan
2019-05-06 7:57 ` Raghav Gururajan
2019-05-06 9:14 ` pelzflorian (Florian Pelz)
2019-05-06 14:05 ` Raghav Gururajan
2019-05-06 19:20 ` Tobias Geerinckx-Rice [this message]
2019-05-06 19:30 ` Raghav Gururajan
2019-05-07 6:29 ` Raghav Gururajan
2019-05-11 9:48 ` Raghav Gururajan
2019-05-11 10:08 ` Ricardo Wurmus
2019-05-11 10:30 ` Raghav Gururajan
2019-07-02 22:44 ` bug#35586: Raghav Gururajan
2019-07-02 23:21 ` bug#35586: SUMMARY (Re-Write) Raghav Gururajan
2019-11-13 5:44 ` bug#35586: GNOME Core Applications Raghav Gururajan
2022-05-25 6:54 ` Roman Riabenko
2022-05-25 11:08 ` Maxime Devos
2022-05-25 17:54 ` Roman Riabenko
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=87zhnzfkz6.fsf@nckx \
--to=me@tobias.gr \
--cc=35586@debbugs.gnu.org \
--cc=rvgn@disroot.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.
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.