unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>, 26988@debbugs.gnu.org
Subject: bug#26988: Add desktop-file-utils to all gtk applications
Date: Sat, 20 May 2017 01:05:22 +0200	[thread overview]
Message-ID: <87inkwa1n1.fsf@fastmail.com> (raw)
In-Reply-To: <20170518230111.53a91ffe@scratchpost.org>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

Danny Milosavljevic <dannym@scratchpost.org> writes:

> these are two patches I propose we add in order to add
> desktop-file-utils to all gtk applications.  This means that the
> profile hook would pick up the desktop files (as soon as possible).

So if I read (guix profiles) correctly, the hook only runs when
'desktop-file-utils' is referenced. Would checking for a gtk reference
as well not achieve the same effect? Or is that too expensive?

> One patch moves desktop-file-utils from (gnu packages gnome) to (gnu
> packages freedesktop).  I suggest we apply this patch to all branches
> - since they don't change anything in the build.

Adding it to 'master' would be sufficient, no? It will be merged to
'staging' and 'core-updates' in due time.

I don't see a good reason to move it though, but no strong opinion. Make
sure all dependent packages still finds it!

> The other patch adds desktop-file-utils as propagated-input to gtk+-2
> (and by inheritance to gtk+ 3, too).  That would imply entail all gtk
> applications.  Therefore, it should only go to core-updates.

Not just all gtk applications, but also anything depending on those. Can
you add a comment about why we propagate 'desktop-file-utils' from gtk?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2017-05-19 23:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 21:01 bug#26988: Add desktop-file-utils to all gtk applications Danny Milosavljevic
2017-05-18 21:07 ` bug#26988: [PATCH] gnu: Move desktop-file-utils to (gnu packages freedesktop) Danny Milosavljevic
2017-05-18 21:19 ` bug#26988: [PATCH] gnu: gtk+-2: Add desktop-file-utils to propagated-inputs Danny Milosavljevic
2017-05-19 23:05 ` Marius Bakke [this message]
2017-05-20 13:04   ` bug#26988: Add desktop-file-utils to all gtk applications Danny Milosavljevic
2017-05-20 23:00     ` Marius Bakke
2017-05-21  2:32       ` Marius Bakke
2017-07-03 15:32         ` 宋文武
2017-07-03 17:08           ` [bug#26988] " Danny Milosavljevic
2017-07-04 11:40             ` 宋文武
2017-06-05 19:22 ` bug#26988: [PATCH v2 0/2] " Danny Milosavljevic
2017-06-05 19:22   ` bug#26988: [PATCH v2 1/2] gnu: Move desktop-file-utils to (gnu packages freedesktop) Danny Milosavljevic
2017-06-15  8:27     ` [bug#26988] " Danny Milosavljevic
2017-06-05 19:22   ` bug#26988: [PATCH v2 2/2] gnu: gtk+-2: Add desktop-file-utils to propagated-inputs Danny Milosavljevic

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=87inkwa1n1.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=26988@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).