all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <raghavgururajan@disroot.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38904@debbugs.gnu.org
Subject: [bug#38904] gnu: Add gnome-color-manager.
Date: Thu, 09 Jan 2020 10:26:31 -0500	[thread overview]
Message-ID: <ec1e5980e5d044eb222039767c9747973c5977e0.camel@disroot.org> (raw)
In-Reply-To: <20200109160313.7adaf490@scratchpost.org>

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

Hi Danny!

> Some questions:
> 
> * Why is adwaita-icon-theme an input?

I believe this application retrives some information about graphical
properties of a-i-t from a-i-t package.

> Some comments:
> 
> * xorg-server-for-tests should definitely be a native-input if it is
> used.
> * desktop-file-utils should definitely be a native-input if it is
> used.
> * itstool should definitely be a native-input if it is used.

Yes, even I believe so. Would it be okay if I leave things as it is for
now? Because soon I will revising+testing all gnome packages one-by-
one, so I will be moving any unnessessary inputs to native-inputs. :-)

Regards,
RG.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-01-09 15:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 19:12 [bug#38904] gnu: Add gnome-color-manager Raghav Gururajan
2020-01-05 10:19 ` Danny Milosavljevic
2020-01-06  5:53   ` Raghav Gururajan
2020-01-08 14:50     ` [bug#38904] v3 Raghav Gururajan
2020-01-09 15:03     ` [bug#38904] gnu: Add gnome-color-manager Danny Milosavljevic
2020-01-09 15:26       ` Raghav Gururajan [this message]
2020-01-09 17:02         ` bug#38904: " Danny Milosavljevic
2020-01-09 17:31           ` [bug#38904] " Raghav Gururajan

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=ec1e5980e5d044eb222039767c9747973c5977e0.camel@disroot.org \
    --to=raghavgururajan@disroot.org \
    --cc=38904@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 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.