From: zimoun <zimon.toutoune@gmail.com>
To: "Léo Le Bouter" <lle-bout@zaclys.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Xinglu Chen" <public@yoctocell.xyz>,
47163@debbugs.gnu.org
Subject: [bug#47163] [PATCH] refresh: Add '--installed' option.
Date: Tue, 16 Mar 2021 13:58:44 +0100 [thread overview]
Message-ID: <CAJ3okZ0JazBeC7kpK24tvh6FBCG6X3P44ZqQ3=BWVobUF=7u0Q@mail.gmail.com> (raw)
In-Reply-To: <c239688b3e196a31a1576cd7e6b764f19b2cfb40.camel@zaclys.net>
Hi Léo,
On Tue, 16 Mar 2021 at 10:18, Léo Le Bouter via Guix-patches via
<guix-patches@gnu.org> wrote:
> I would also really like such option for 'lint' and 'refresh' that can
> take an operating-system definition so I can ensure a certain set of
> packages are up to some standards and help me focus my efforts on my or
> some fellow's configuration (especially w.r.t. security), rather than
> randomly trying to maintain *everything* in the GNU Guix repo which is
> quite exhausting and large work to take on. Starting from a place of
> actual need for myself and some fellow's configurations looks like a
> more achieveable goal mid-term.
Adding the manifest option to "guix lint", is it not enough? I do not
know how many packages you have in your operating-system definition
but from my understanding your user-wide packages should be in
manifest.scm files, and you could also maintain a manifest.scm file
for your packages system-wide. Anyway.
Here an example with an hard-coded path, saved in /tmp/manifest-from-os.scm:
--8<---------------cut here---------------start------------->8---
(use-modules
(gnu system)
(guix profiles))
(define os
(load "/home/simon/src/guix/guix/gnu/system/examples/bare-bones.tmpl"))
(define pkgs (operating-system-packages os))
(packages->manifest pkgs)
--8<---------------cut here---------------end--------------->8---
Then "guix refresh -m /tmp/manifest-from-os.scm" should do the job.
Well, it is an example, the point is simply to show that an option is
not necessary, IMHO. However, a robust script could be in etc/ with
some other tools and with a line in the manual. Maybe. :-)
It seems better to keep separated what operates on packages and what
operates on system.
Cheers,
simon
next prev parent reply other threads:[~2021-03-16 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 15:45 [bug#47163] [PATCH] refresh: Add '--installed' option Xinglu Chen
2021-03-15 20:38 ` Ludovic Courtès
2021-03-15 21:14 ` Xinglu Chen
2021-03-16 9:08 ` Ludovic Courtès
2021-03-16 9:16 ` Léo Le Bouter via Guix-patches via
2021-03-16 12:58 ` zimoun [this message]
2021-03-16 13:10 ` Léo Le Bouter via Guix-patches via
2021-03-16 16:05 ` Xinglu Chen
2021-03-16 16:44 ` [bug#47163] Using package transformations declaratively (was: [bug#47163] [PATCH] refresh: Add '--installed' option.) Xinglu Chen
2021-03-16 17:23 ` zimoun
2021-03-16 18:35 ` Xinglu Chen
2021-03-17 17:17 ` [bug#47163] Using package transformations declaratively Ludovic Courtès
2021-03-16 16:19 ` [bug#47163] [PATCH] doc: Add snippet for running 'guix refresh' on installed packages Xinglu Chen
2021-03-16 18:06 ` Ludovic Courtès
2021-03-16 18:34 ` Xinglu Chen
2021-03-18 9:31 ` Ludovic Courtès
2021-03-17 12:23 ` [bug#47213] [PATCH v2] doc: Add snippet for running 'guix refresh' on installed Xinglu Chen
2021-03-25 16:15 ` Xinglu Chen
2021-03-25 23:21 ` bug#47213: " Ludovic Courtès
2021-03-26 17:18 ` bug#47163: [PATCH] refresh: Add '--installed' option Xinglu Chen
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='CAJ3okZ0JazBeC7kpK24tvh6FBCG6X3P44ZqQ3=BWVobUF=7u0Q@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=47163@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
--cc=ludo@gnu.org \
--cc=public@yoctocell.xyz \
/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.