unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <rvgn@disroot.org>
To: 35586@debbugs.gnu.org
Subject: bug#35586: GNOME
Date: Sun, 05 May 2019 14:20:39 -0400	[thread overview]
Message-ID: <c99df64bf65aed4210c059cc2ff5628129be9abc.camel@disroot.org> (raw)

Hello Guix!

Based on the mail-list thread "https://lists.gnu.org/archive/html/help-
guix/2019-05/msg00124.html", it appears that there is a bug, where some
GNOME Core Applications are actually packaged in guix but have not been
included in guix's "gnome" package.

So I did [guix search "gnome-*"] and cross-checked the results with
guix's gnome package source (https://git.savannah.gnu.org/cgit/guix.git
/tree/gnu/packages/gnome.scm?id=v0.16.0-5851-g5f83b5153a#n6422); and
found out that the following gnome core application packages are indeed
packaged in guix, but have not been included in guix's gnome package. 

gnome-calendar
gnome-clocks
gnome-common
gnome-desktop
gnome-dictionary
gnome-doc-utils
gnome-icon-theme
gnome-klotski
gnome-maps
gnome-mime-data
gnome-mines
gnome-mpv
gnome-planner
gnome-screenshot
gnome-shell-extensions
gnome-sudoku
gnome-todo
gnome-tweak-tool
gnome-vfs
gnome-video-effects

The following gnome core applications are also already packaged in guix
but requires correct renaming before adding to guix's gnome package?

rhythmbox --> gnome-music
shotwell --> gnome-photos

The following gnome core applications have already been included in
guix's gnome package but requires correct renaming?

epiphany --> gnome-web
envice --> gnome-documents
eog --> gnome-images
file-roller --> gnome-autoar
gedit --> gnome-text
nautilus --> gnome-files

I really hope if the above modifications are made, it will fulfill the
actual description of guix's gnome package (http://guix.gnu.org/package
s/gnome-3.28.2/). ☺

Thank you!

Regards,
RG.

             reply	other threads:[~2019-05-05 18:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-05 18:20 Raghav Gururajan [this message]
2019-05-05 18:52 ` bug#35586: GNOME 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
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

  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=c99df64bf65aed4210c059cc2ff5628129be9abc.camel@disroot.org \
    --to=rvgn@disroot.org \
    --cc=35586@debbugs.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).