From: ng0 <ng0@n0.is>
To: Marco van Hulten <marco@hulten.org>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: xdm
Date: Tue, 26 Nov 2019 14:06:28 +0000 [thread overview]
Message-ID: <20191126140628.lngiqib4hfo76gwq@uptimegirl> (raw)
In-Reply-To: <20191022154858.306e1deb@gfi063209.klientdrift.uib.no>
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).
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.
next prev parent reply other threads:[~2019-11-26 14:06 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 ` ng0 [this message]
2019-12-03 14:52 ` xdm Marco van Hulten
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=20191126140628.lngiqib4hfo76gwq@uptimegirl \
--to=ng0@n0.is \
--cc=help-guix@gnu.org \
--cc=marco@hulten.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.
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).