all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Bernd S." <Rs1R8ng1@protonmail.ch>
To: "ludo@gnu.org" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: let's talk about SLIM
Date: Fri, 01 Sep 2017 18:34:19 -0400	[thread overview]
Message-ID: <4Eb_zD7QAF9uMVwWrhO5zz1J_L8zG9KUGmHTOtgEHl56P2b3UcFN1b-k6VrORX7E3aTLKkBFuz9ZsgBIMmrmKkKth8RVQsmlm3tuLe1PSUk=@protonmail.ch> (raw)
In-Reply-To: <87inh577xs.fsf@gnu.org>

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

I agree as well that SLiM should be replaced as the default display manager,
for one because of the problems mentioned, and also because it is no longer
maintained.

I also agree that the replacement should be something really lightweight and independent,
I really like the suggestion of OpenBSDs xenodm for example.

I do not think that gdm would be a good base default option, it should rather be used
as the default for using %desktop-services with Gnome, as already suggested.

> Hi,
>
> Mark H Weaver <mhw@netris.org> skribis:
>
>> ng0 <ng0@infotropique.org> writes:
>>
>>> It seems to me as if SLIM can be dropped once we
>>> have something else in place. Would you agree?
>>
>> It would be good to keep a display manager service that is lightweight
>> in terms of both resource usage, runtime-dependency closure, and
>> build-dependency closure. I"m not attached to SLiM, but I would not
>> consider the existence of a GDM service to be sufficient grounds for
>> removal of SLiM.
>>
>> Apart from the needs of those on older hardware, or those who wish to
>> build everything locally from source code, I"m not sure if we"ve ever
>> successfully built GDM on a non-Intel system. GDM depends on mozjs-17,
>> which I"ve never managed to build on mips64el-linux, and it fails on
>> armhf-linux too. Fixing mozjs on mips64el-linux is probably not
>> trivial, and yet I"m happily using SLiM on my Yeeloong, which is still
>> the only non-Intel GuixSD system as far as I know.
>
> I agree we should not remove SLiM. I think the question is more about
> the default we want to have.
>
> For people using %desktop-services with GNOME and all that, it probably
> makes sense to default to GDM.
>
> For the lightweight-desktop example, it may makes sense to stick to a
> lightweight login tool.
>
> One grief I have against SLiM is that it lacks i18n support. If lightdm
> fixes that, I would recommend it instead of SLiM in the
> lightweight-desktop example. I haven’t investigated though.
>
> Thoughts?
>
>> Personally, I"d be much happier with a working system that could be
>> audited and not have the audit become stale before its completion. The
>> amount of code churn in my systems is so great that it"s infeasible for
>> me to audit all of the changes coming down the pipe. I find that very
>> uncomfortable.
>
> On one hand I sympathize (I don’t use GNOME/KDE/Xfce and have long tried
> to avoid tools depending on the whole Freedesktop stack in my “base”
> system), but on the other hand, I think we have to realize that (1) no
> single individual can audit more than a tiny fraction of their system,
> and (2) when it comes to running a full desktop environment, we’re even
> further away from that goal anyway, GDM or not.
>
> Thanks,
> Ludo’.

[-- Attachment #2: Type: text/html, Size: 3746 bytes --]

  parent reply	other threads:[~2017-09-01 22:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-26 21:32 let's talk about SLIM ng0
2017-08-27 20:08 ` Mark H Weaver
2017-08-27 23:40   ` Adam Van Ymeren
2017-08-28 15:33   ` Efraim Flashner
2017-08-30  8:53   ` Ludovic Courtès
2017-08-30  9:18     ` ng0
2017-08-30  9:26       ` ng0
2017-09-01 22:34     ` Bernd S. [this message]
2017-09-03  4:07       ` Adam Van Ymeren
2017-09-02  9:40     ` Mark H Weaver

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='4Eb_zD7QAF9uMVwWrhO5zz1J_L8zG9KUGmHTOtgEHl56P2b3UcFN1b-k6VrORX7E3aTLKkBFuz9ZsgBIMmrmKkKth8RVQsmlm3tuLe1PSUk=@protonmail.ch' \
    --to=rs1r8ng1@protonmail.ch \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.