From: Efraim Flashner <efraim@flashner.co.il>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Subject: Re: Automatically testing package updates
Date: Thu, 5 Dec 2024 09:20:53 +0200 [thread overview]
Message-ID: <Z1FUVR2sJvIWe76u@3900XT> (raw)
In-Reply-To: <87a5ddoq2r.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
On Mon, Dec 02, 2024 at 08:14:04PM +0100, Simon Tournier wrote:
> Hi,
>
> On Mon, 02 Dec 2024 at 14:44, Ludovic Courtès <ludo@gnu.org> wrote:
>
> > This manifest is just an example. We could come up with manifests
> > targeting package collections like CRAN packages, astronomy packages,
> > and so on.
>
> Let consider that a “leaf” package is a package that does not appear
> elsewhere in any other packages. Then, if there is no mistake, I count
> 14143 leaf packages over 32459 all packages.
>
> Well, if we filter using gnu-build-system and cmake-build-system then it
> reduces to 2847 packages.
>
> These packages are “safe” to automatically update because the only
> annoyance will be users at run time. ;-)
>
> Somehow, the loop and type conversion are not optimized but maybe this
> kind of “leaf” packages could defined and then filtered build-system per
> build-system, i.e., team per team.
>
> WDYT?
To repeat what I said on Mastodon and the impression I got from the Nix
folks, if we can automate away the easy/simple package upgrades then we
can spend our time on more complex upgrades that require more attention
to get correct.
I'm now thinking about the easy-package -> hard-package learning curve
for new contributors, and I'm not sure how we'd address that.
Also I don't think we should spam the bug tracker with package upgrades,
so we'd have to think about something for that.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-05 7:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 13:44 Automatically testing package updates Ludovic Courtès
2024-12-02 14:50 ` Simon Tournier
2024-12-02 19:14 ` Simon Tournier
2024-12-02 19:16 ` Simon Tournier
2024-12-05 7:20 ` Efraim Flashner [this message]
2024-12-05 8:06 ` Hilton Chain
2024-12-05 9:23 ` Ricardo Wurmus
2024-12-05 13:29 ` Suhail Singh
2024-12-05 15:31 ` Ricardo Wurmus
2024-12-05 16:10 ` Suhail Singh
2024-12-05 19:07 ` Attila Lendvai
2024-12-05 19:55 ` Ricardo Wurmus
2024-12-06 5:09 ` Suhail Singh
2024-12-14 23:46 ` Ludovic Courtès
2024-12-06 4:53 ` Suhail Singh
2024-12-05 19:58 ` Ricardo Wurmus
2024-12-03 0:32 ` Vagrant Cascadian
2024-12-14 23:47 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 14:01 Sharlatan Hellseher
2024-12-14 23:51 ` 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=Z1FUVR2sJvIWe76u@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.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 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).