From: Raghav Gururajan <rvgn@disroot.org>
To: guix-devel@gnu.org
Subject: GNOME
Date: Mon, 06 May 2019 11:24:01 -0400 [thread overview]
Message-ID: <43d6a380f89f337033ec4cffa0bc1afa0c8a6ea2.camel@disroot.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1182 bytes --]
To Ricardo Wurmus, Timothy Sample and Mark H Weaver!
Regarding GNOME Core Applications and modifications to current "gnome"
package, FYI, I have filed this https://debbugs.gnu.org/cgi/bugreport.c
gi?bug=35586.
Recently, I have been given this link (https://wiki.gnome.org/Design/Ap
ps) 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 --> GNOME Core Libraries+Utilities+Services+Apps
gnome-minimal --> GNOME Core Libraries+Utilities+Services ( Provides
only dm, wm, menus, settings etc. witout any 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".
Thank you!
Regards,
RG.
[-- Attachment #2: Type: text/html, Size: 1613 bytes --]
next reply other threads:[~2019-05-06 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 15:24 Raghav Gururajan [this message]
2019-05-06 16:03 ` GNOME Raghav Gururajan
-- strict thread matches above, loose matches on Subject: below --
2019-05-02 5:20 GNOME Raghav Gururajan
2019-05-02 6:18 ` GNOME znavko
2019-05-03 1:55 ` GNOME Mark H Weaver
2019-05-03 6:47 ` GNOME Raghav Gururajan
2016-03-18 21:22 GNOME rennes
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=43d6a380f89f337033ec4cffa0bc1afa0c8a6ea2.camel@disroot.org \
--to=rvgn@disroot.org \
--cc=guix-devel@gnu.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 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).