From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Dariqq <dariqq@posteo.net>,
57292@debbugs.gnu.org, 59489@debbugs.gnu.org,
Vivien Kraus <vivien@planete-kraus.eu>,
Raghav Gururajan <rg@raghavgururajan.name>
Subject: bug#57292: [PATCH] WIP: gnu: propagate inputs for gdm and rework gdm-service-type.
Date: Fri, 09 Feb 2024 22:06:47 -0500 [thread overview]
Message-ID: <87r0hlvwzc.fsf@gmail.com> (raw)
In-Reply-To: <f3ed3053b5db03a53255e917eb348ab2a4bfb151.camel@gmail.com> (Liliana Marie Prikler's message of "Mon, 05 Feb 2024 18:55:47 +0100")
Hello,
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Am Montag, dem 05.02.2024 um 16:08 +0000 schrieb Dariqq:
>>
>> On 04.02.24 20:26, Liliana Marie Prikler wrote:
>>
>> > Yes, it seems Maxim and I have conflicting goals. Maxim wants to
>> > avoid "abusing" gnome-shell-assets whereas I want to avoid
>> > propagation, as it pollutes profiles. Perhaps Maxim and I can
>> > agree on how to interpret gnome-shell-assets, as IIUC even with
>> > packages that aren't "pure data" only the data portion of it ought
>> > to be relevant, no?
>> >
>> > We should do so especially because the newly propagated variables
>> > are anyhow propagated by gnome-desktop-service, which could
>> > constitute weird behaviour all around.
>> >
>> > Cheers
>>
>> What would you think of the wrap-program solution which would avoid
>> propagating pacakges?
>>
>> I currently have something like
>>
>> #+BEGIN_SRC scheme
>> (add-after 'install 'wrap-gdm
>> (lambda* (#:key inputs outputs #:allow-other-keys)
>> (wrap-program (string-append #$output "/bin/gdm")
>> `("XDG_DATA_DIRS" ":" prefix
>> #$(map (lambda (input)
>> (file-append (this-package-input input)
>> "/share"))
>> '("at-spi2-core"
>> "dconf"
>> "gnome-control-center"))))))
>> #+END_SRC
>>
>> Also this way the assets (adwaita and cantarell) should be kept in
>> the gdm-configuration as when I tested this I had a white box as a
>> cursor.
> That SGTM, but we do need a more descriptive phase name. The question
> is whether we should inline the gnome-shell assets this way as well or
> not.
I have never attempted to customize gnome-shell. If it can be
customized with custom themes, different fonts and what not, then I
think it makes sense to keep the user-choosable art assets as
gnome-shell-assets.
Otherwise, if it's not configurable and expects only a specific font,
specific icons, etc., then it seems it'd make sense that it finds them
out of the gate (wrapped from within a phase).
Could someone confirm whether GDM is configurable when it comes to icons
and fonts?
Thanks for working on it, Dariqq!
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-02-10 3:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 2:11 bug#57292: GDM accessibility menu buttons don't do anything Maxim Cournoyer
2022-09-18 19:36 ` Liliana Marie Prikler
2024-01-16 20:49 ` bug#57292: [PATCH] services: gdm: Add packages for accessibility settings Dariqq
2024-01-20 3:12 ` bug#57292: bug#59489: gdm: Accessibility icon missing in log in screen Maxim Cournoyer
2024-01-20 17:09 ` Dariqq
2024-01-22 5:30 ` Maxim Cournoyer
2024-01-22 18:51 ` Dariqq
2024-01-16 21:09 ` bug#57292: GDM accessibility menu buttons don't do anything Dariqq
2024-01-29 21:31 ` bug#57292: [PATCH] WIP: gnu: propagate inputs for gdm and rework gdm-service-type Dariqq
2024-01-30 5:27 ` bug#59489: " Liliana Marie Prikler
2024-02-04 8:53 ` Dariqq
2024-02-04 19:26 ` Liliana Marie Prikler
2024-02-05 16:08 ` Dariqq
2024-02-05 17:55 ` Liliana Marie Prikler
2024-02-10 3:06 ` Maxim Cournoyer [this message]
2024-02-12 14:02 ` bug#59489: " Liliana Marie Prikler
2024-02-13 21:25 ` Dariqq
2024-02-16 19:10 ` bug#57292: GDM accessibility menu buttons don't do anything Maxim Cournoyer
2024-02-20 19:58 ` bug#57292: [PATCH v3] gnu: gdm: Enable accessibility settings Dariqq
2024-02-24 6:38 ` bug#59489: " Liliana Marie Prikler
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 20:36 bug#59489: gdm: Accessibility icon missing in log in screen Luis Felipe via Bug reports for GNU Guix
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=87r0hlvwzc.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=57292@debbugs.gnu.org \
--cc=59489@debbugs.gnu.org \
--cc=dariqq@posteo.net \
--cc=liliana.prikler@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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).