From: "Raghav Gururajan" <rvgn@disroot.org>
To: rekado@elephly.net, clement@lassieur.org, me@tobias.gr
Cc: 35586@debbugs.gnu.org
Subject: bug#35586: GNOME
Date: Tue, 07 May 2019 06:29:16 +0000 [thread overview]
Message-ID: <7a8b3492f9882d4179cb114136de7e92@disroot.org> (raw)
In-Reply-To: <e2d35da2991336f8723ebbbeb92d5e57@disroot.org>
Hello!
Recently, I have been given this link (https://wiki.gnome.org/Design/Apps) which lists all GNOME Core Applications that are to be added to guix's gnome package.
Whether or not to do this, I think the package with the name "gnome" in any distribution should always reflect the vanilla gnome suite released by GNOME Project. Any modification to it, I think, should be packaged under different name like "gnome-minimal" or gnome-extras" etc. This can be a good standard.
My suggestion is,
gnome --> With All Core Apps
gnome-minimal --> Without Any Core Apps (Provides only xorg/wayland, dm, wm, menus, drivers, services etc.)
** INFO: Core Apps can be found at https://wiki.gnome.org/Design/Apps. **
Also, based on the above, I think we also need to create/enable new value "gnome-minimal" for the data type "gnome-desktop-configuration" of the variable "gnome-desktop-service-type". Value "gnome" can still be default though. Power users can change the value to "gnome-minimal".
This can provide good modularity and thus provides choices to users. For example, 1) If a user needs full-blown GNOME, "gnome" can be chosen, 2) If a user needs only minimal GNOME, "gnome-minimal" can be chosen, 3) If a user needs minimal GNOME with select core apps, "gnome-minimal" can be chosen under service and individual needed core apps can be added under system packages.
Also, it would be a good standard to use generic names for packaging as recommended at https://blogs.gnome.org/mcatanzaro/2016/09/21/gnome-3-22-core-apps. Other alias-names/project names can be included in package's description.
Thank you!
Regards,
RG.
May 6, 2019 7:30 PM, "Raghav Gururajan" <rvgn@disroot.org> wrote:
> T-G-R!
>
> Thanks for your email. I understand what you mentioned. I came across this link
> (https://blogs.gnome.org/mcatanzaro/2016/09/21/gnome-3-22-core-apps), where the dev(s) recommend to
> use generic names while packaging GNOME Core Apps. :)
>
> I think it is better to use generic names for package names and include other aliases/project-names
> in the package tagline and/or package description.
>
> May 6, 2019 7:20 PM, "Tobias Geerinckx-Rice" <me@tobias.gr> wrote:
>
>> 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
next prev parent reply other threads:[~2019-05-07 6:30 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
2019-05-06 19:30 ` Raghav Gururajan
2019-05-07 6:29 ` Raghav Gururajan [this message]
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=7a8b3492f9882d4179cb114136de7e92@disroot.org \
--to=rvgn@disroot.org \
--cc=35586@debbugs.gnu.org \
--cc=clement@lassieur.org \
--cc=me@tobias.gr \
--cc=rekado@elephly.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.