unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Mark H Weaver <mhw@netris.org>,bo0od <bo0od@riseup.net>
Cc: 47748@debbugs.gnu.org
Subject: bug#47748: Packages which cant be find/removed by guix remove
Date: Wed, 14 Apr 2021 06:34:21 -0400	[thread overview]
Message-ID: <21094992-5632-4D68-B051-2A13AE61AC1C@lepiller.eu> (raw)
In-Reply-To: <87sg3tr3dh.fsf@netris.org>

Le 13 avril 2021 22:44:31 GMT-04:00, Mark H Weaver <mhw@netris.org> a écrit :
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> Second, your operating-system declaration apparently is running
>> the avahi server. Since you didn't share it, I don't know if it comes
>> from a service dependency or if it's declared explicitely,
>
>The avahi service is included in '%desktop-services'.
>
>https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/desktop.scm?id=a758a8a3c20052c5f1228e1ec80068652bbc3849#n1267
>
>I don't know off-hand what is the current recommended way to remove
>unwanted services from convenience variables like '%desktop-services'.
>I suppose something like this (untested) in place of
>'%desktop-services':
>
>__ (remove (lambda (svc)
>____________ (eq? (service-kind svc) avahi-service-type))
>__________ %desktop-services)
>
>with at least the following modules included at the top of the file:
>
>__ (use-modules (gnu services)
>_______________ (gnu services avahi)
>_______________ (srfi srfi-1))
>
>My own longstanding (and questionable) approach has been to avoid using
>'%desktop-services', and instead to inline its contents into my OS
>config, minus the stuff I don't want.  However, if you choose to use
>that method, it's probably a good idea to periodically check for
>changes
>to '%desktop-services', and to integrate those changes into your own
>config where appropriate.
>
>        Mark

The manual suggests modify-services in some places:

(modify-services %desktop-services
  (delete avahi-service-type))




  reply	other threads:[~2021-04-14 10:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 12:46 bug#47748: Packages which cant be find/removed by guix remove bo0od
2021-04-14  0:28 ` Julien Lepiller
2021-04-14  2:44   ` Mark H Weaver
2021-04-14 10:34     ` Julien Lepiller [this message]
2021-04-14 16:07       ` Mark H Weaver
2021-04-16 14:52         ` Mark H Weaver
2021-04-14 16:31   ` bo0od
2021-04-14 18:42     ` Mark H Weaver
2021-04-15  9:26       ` bo0od
2021-04-15 19:34         ` Mark H Weaver
2021-04-16  2:45           ` bo0od
2021-04-14 18:44     ` Maxime Devos
2021-04-15  9:37       ` bo0od
2021-04-15 18:04         ` Maxime Devos
2021-04-16  2:58           ` bo0od
2021-04-14 18:48     ` Julien Lepiller
2021-04-15 10:16       ` bo0od
2021-04-15 11:03         ` Julien Lepiller
2021-04-16  2:11           ` bo0od
2021-04-16  3:41             ` Leo Famulari
2021-04-16  4:37               ` bo0od
2021-04-16  7:23                 ` Leo Famulari

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=21094992-5632-4D68-B051-2A13AE61AC1C@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=47748@debbugs.gnu.org \
    --cc=bo0od@riseup.net \
    --cc=mhw@netris.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 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).