all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marco van Hulten <marco@hulten.org>
To: ng0@n0.is
Cc: help-guix@gnu.org
Subject: Re: xdm
Date: Tue, 3 Dec 2019 15:52:48 +0100	[thread overview]
Message-ID: <20191203155248.0b2e7f5f@gfi063209.klientdrift.uib.no> (raw)
In-Reply-To: <20191126140628.lngiqib4hfo76gwq@uptimegirl>

On 26 Nov 14:06 ng0 wrote:
> I have bits of an xdm package somewhere in my vault/archive of
> "packages to send to guix once I find time to contribute again".
> 
> What makes it more complicated / time consuming with xdm is that
> you need to figure out the service for it.
> 
> If you or anyone else wants to work on it, I can send a patch (external, not applying to
> guix.git).

To be honest, I have not allocated enough time for Guix development for
any significant contribution like an xdm package.  I hope 2020 will be
better.  I hope someone else wants to work on it before that time (but
in my current Guix installations the desktop manager, whichever this
is, works properly).  In any case, I can make time for testing Guix
code if that is useful at all.

> Fwiw, I looked at the work OpenBSD does with their X11 patching (for more time than I am willing to admit),
> and it's not worth to extract and re-apply the meaningful patches
> for one single project. I don't get why parabola is re-purposing this X11 work,
> but OpenBSD work is usually written for OpenBSD with an underlying OpenBSD
> system in mind. That's not to say their X11 is "useless", it's just useful
> in OpenBSD.

Point taken.  Seems reasonable.

—Marco

      reply	other threads:[~2019-12-03 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 13:48 xdm Marco van Hulten
2019-11-26 14:06 ` xdm ng0
2019-12-03 14:52   ` Marco van Hulten [this message]

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=20191203155248.0b2e7f5f@gfi063209.klientdrift.uib.no \
    --to=marco@hulten.org \
    --cc=help-guix@gnu.org \
    --cc=ng0@n0.is \
    /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.