From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, mail@cbaines.net
Subject: Re: Fedora/Debian release monitoring inspiration for Guix Data Service
Date: Wed, 17 Mar 2021 18:47:52 +0100 [thread overview]
Message-ID: <e58e84144f2cd0f53735d2d61590efac5764cc7a.camel@zaclys.net> (raw)
In-Reply-To: <877dm51y5i.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
On Wed, 2021-03-17 at 18:35 +0100, Ludovic Courtès wrote:
> Established distros have great tools and services for that.
>
> Guix has ‘guix refresh’, which predates some of the trendy
> release/CVE
> monitoring services and actually works well. It’s not perfect, but
> it’s
> good, so my advice would be to work on improving it.
>
> If you look at Guix’s design and history, you’ll find that much is
> built
> in a way that avoids relying on external services when we can.
Just to clarify, I also get behind that very much I was suggesting the
functional part more so than the service kind, even though I think
services (like Guix Data Service) are OK as long as datasets are easily
exportable and the service itself can easily be re-deployed through GNU
Guix as well.
It seems GNU Guix takes a generic approach to updates while Debian or
Fedora seems to look at specialized rules for each package, I was
thinking we could import those already existing rules (in Fedora's or
Debian's) into GNU Guix, I find it a superior approach for reliability
of notifications even though generic updaters are also very
complementary.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-17 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 10:57 Fedora/Debian release monitoring inspiration for Guix Data Service Léo Le Bouter
2021-03-16 11:12 ` Ricardo Wurmus
2021-03-16 11:14 ` Léo Le Bouter
2021-03-16 23:28 ` Christopher Baines
2021-03-17 10:24 ` Léo Le Bouter
2021-03-17 17:35 ` Ludovic Courtès
2021-03-17 17:47 ` Léo Le Bouter [this message]
2021-03-20 11:22 ` Ludovic Courtès
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=e58e84144f2cd0f53735d2d61590efac5764cc7a.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
/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).