From: Danny Milosavljevic <dannym@scratchpost.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Move gtkglext from gnome to gtk.
Date: Tue, 16 Aug 2016 22:40:00 +0200 [thread overview]
Message-ID: <20160816224000.6bfbbbd5@scratchpost.org> (raw)
In-Reply-To: <20160816201407.GD20269@jasmine>
> Okay. Do the games and engineering modules still need to import the
> gnome module if we make this move?
Yes.
The reasons that they still need gnome.scm are:
- engineering.scm references desktop-file-utils and shared-mime-info which are freedesktop things (i.e. common to all desktop environments) but are inside gnome.scm .
- games.scm references librsvg which is inside gnome.scm for some reason.
But I wanted to avoid the dependency in education.scm for celestia.
Right now, gnome.scm includes gtk.scm and gtk.scm includes gnome.scm because of the above, among other things.
Disentangling all that seems to be a lot of work for little gain - however, I don't understand why there's gtk.scm and gnome.scm in the first place if we don't distinguish between them. It makes sense to distinguish since lxde, xfce, gnome etcetc all use gtk and freedesktop stuff.
next prev parent reply other threads:[~2016-08-16 20:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 18:01 [PATCH] gnu: Move gtkglext from gnome to gtk Danny Milosavljevic
2016-08-16 20:03 ` Leo Famulari
2016-08-16 20:09 ` Danny Milosavljevic
2016-08-16 20:14 ` Leo Famulari
2016-08-16 20:40 ` Danny Milosavljevic [this message]
2016-08-16 23:12 ` Danny Milosavljevic
2016-08-16 23:14 ` [PATCH] gnu: move freedesktop stuff to "freedesktop.scm", gtk stuff to "gtk.scm", gnome stuff to "gnome.scm" Danny Milosavljevic
2016-08-16 23:40 ` [PATCH] gnu: Move gtkglext from gnome to gtk Leo Famulari
2016-08-16 23:42 ` Leo Famulari
2016-08-17 6:53 ` Ricardo Wurmus
2016-08-20 8:53 ` Efraim Flashner
2016-08-22 8:56 ` ng0
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=20160816224000.6bfbbbd5@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).