From: "Ludovic Courtès" <ludo@gnu.org>
To: Josh Holland <josh@inv.alid.pw>
Cc: 37991@debbugs.gnu.org
Subject: [bug#37991] (no subject)
Date: Thu, 07 Nov 2019 21:10:33 +0100 [thread overview]
Message-ID: <87d0e3qwg6.fsf@gnu.org> (raw)
In-Reply-To: <87wocd6nbh.fsf@inv.alid.pw> (Josh Holland's message of "Wed, 06 Nov 2019 15:23:30 +0000")
Hi Josh,
Josh Holland <josh@inv.alid.pw> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>> Could you check ‘guix size redshift’ vs. ‘guix size redshift-wayland’,
>> to estimate the cost of supporting both X and Wayland?
> $ ./pre-inst-env guix size redshift
[...]
> total: 126.6 MiB
>
> $ ./pre-inst-env guix size redshift-wayland
[...]
> total: 136.7 MiB
>
>
>> If the cost in size is too important, then we could keep separate
>> packages, but in that case one should inherit from the other to reduce
>> duplication.
>
> I agree, but IMO 10 MiB is fairly insignificant. My only reservation is
> that this isn't a formally released package, but I've been using it for
> a week or so without any issues (though I haven't tested it on an X11
> system).
I agree.
So, could you send a patch that updates ‘redshift’ to this snapshot and
adds Wayland support? Just add a comment stating why we’re using this
snapshot instead of the latest release.
Thanks!
Ludo’.
next prev parent reply other threads:[~2019-11-07 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 13:08 [bug#37991] [PATCH] gnu: Add redshift-wayland Josh Holland
2019-10-30 13:14 ` [bug#37991] (no subject) Josh Holland
2019-11-04 22:09 ` Ludovic Courtès
2019-11-06 15:23 ` Josh Holland
2019-11-07 20:10 ` Ludovic Courtès [this message]
2019-11-09 23:14 ` Marius Bakke
2019-11-16 16:41 ` bug#37991: " Ludovic Courtès
2019-11-08 10:13 ` [bug#37991] [PATCH] gnu: redshift: Use fork with support for Wayland Josh Holland
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=87d0e3qwg6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=37991@debbugs.gnu.org \
--cc=josh@inv.alid.pw \
/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.