From: Tomas Volf <~@wolfsden.cz>
To: Fabio Natali <me@fabionatali.com>
Cc: 68289@debbugs.gnu.org
Subject: [bug#68289] [PATCH] services: xorg: Add xorg-start-command-xinit procedure.
Date: Thu, 18 Apr 2024 23:17:40 +0200 [thread overview]
Message-ID: <ZiGN9OhfIYS2I_EG@ws> (raw)
In-Reply-To: <87jzkufr4y.fsf@fabionatali.com>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
On 2024-04-18 19:43:41 +0100, Fabio Natali wrote:
> On 2024-04-17, 10:30 +0100, Fabio Natali <me@fabionatali.com> wrote:
> > Hi, a quick follow-up on a couple of points.
>
> Also, I suppose one could use Guix's 'invoke' instead of a custom
> 'checked-system*'?
>
> https://issues.guix.gnu.org/issue/68289/#0-lineno88
>
> Cheers, F.
Yes, that would be an option. I do not remember why I wrote it like this, it is
possible I just did not know about `invoke' at that time (the code is over a
year old). However I am not sure whether it is fine to depend on code in the
(guix build utils) module for non-build purposes. Assuming it is fine, I have
no problem sending a v2.
Cheers,
T.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-04-18 21:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-06 15:07 [bug#68289] [PATCH] services: xorg: Add xorg-start-command-xinit procedure Tomas Volf
2024-04-16 18:29 ` Fabio Natali via Guix-patches via
2024-04-17 9:30 ` Fabio Natali via Guix-patches via
2024-04-18 18:43 ` Fabio Natali via Guix-patches via
2024-04-18 21:17 ` Tomas Volf [this message]
2024-04-18 21:09 ` Tomas Volf
2024-04-19 12:25 ` Fabio Natali via Guix-patches via
2024-04-24 11:59 ` Fabio Natali via Guix-patches via
2024-04-24 17:43 ` Tomas Volf
2024-05-02 9:55 ` Ludovic Courtès
2024-05-02 14:58 ` Tomas Volf
2024-05-03 9:57 ` Ludovic Courtès
2024-05-11 13:29 ` Tomas Volf
2024-05-11 13:26 ` [bug#68289] [PATCH v2 1/3] " Tomas Volf
2024-05-11 13:26 ` [bug#68289] [PATCH v2 2/3] services: xorg: Add startx-command-service-type Tomas Volf
2024-05-11 13:26 ` [bug#68289] [PATCH v2 3/3] home: services: Add home-startx-command-service-type Tomas Volf
2024-05-30 17:33 ` [bug#68289] [PATCH] services: xorg: Add xorg-start-command-xinit procedure Arun Isaac
2024-05-30 18:27 ` Tomas Volf
2024-05-30 18:18 ` [bug#68289] [PATCH v3 1/2] services: xorg: Add startx-command-service-type Tomas Volf
2024-05-30 18:18 ` [bug#68289] [PATCH v3 2/2] home: services: Add home-startx-command-service-type Tomas Volf
2024-05-30 18:29 ` [bug#68289] [PATCH v4 1/2] services: xorg: Add startx-command-service-type Tomas Volf
2024-05-30 18:29 ` [bug#68289] [PATCH v4 2/2] home: services: Add home-startx-command-service-type Tomas Volf
2024-05-30 21:43 ` bug#68289: [PATCH] services: xorg: Add xorg-start-command-xinit procedure Arun Isaac
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=ZiGN9OhfIYS2I_EG@ws \
--to=~@wolfsden.cz \
--cc=68289@debbugs.gnu.org \
--cc=me@fabionatali.com \
/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.