unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: gnu: inetutils: Update to 2.4.
Date: Tue, 14 Mar 2023 20:49:03 +0100	[thread overview]
Message-ID: <ZBDPr71maZqhszLT@jurong> (raw)
In-Reply-To: <CAFHYt55otH2BOk9QAeuNo=-64v1Dg_p7rnmBk7ZvR5mMgRLu7A@mail.gmail.com>

Hello Felix,

Am Tue, Mar 14, 2023 at 09:37:23AM -0700 schrieb Felix Lechner via Development of GNU Guix and the GNU System distribution.:
> With the core-updates process now abandoned, I retitled the issue to
>     "[PATCH wip-inetutils 0/4] gnu: inetutils: Update to 2.4".

apologies for not replying earlier - this was because I did not have the
answer... I think this is a place where the feature branch idea is not yet
fully thought out. It is quite clear how branches closer to the leaves
could work (language branches, a qt/kde branch, such things); and probably
also "core things". There I see two kinds of cores: First, things that are
very close to Guile/Guix (switching to gexps, rewriting the daemon in Guile,
these kind of things). And maybe something more like "bootstrap" and "tool-
chain" (changing the Guile version, updating gcc/mpfr/mpc, probably rust,
and so on).

I do not yet have a clear picture for things on a "middle level", but which
cause a lot of rebuilds. Which kind of team would be responsible for
inetutils?

Suggestions would be very welcome!

Something completely different: I am not sure whether inetutils should have
so many dependencies. It only contains binaries and no libraries. For
instance, it is sometimes used as native input for tests, but tests do not
have access to the inet anyway. So maybe it would make sense to identify
the "root" where this package is pulled in, drop the input and modify
the test suite?

Andreas



  reply	other threads:[~2023-03-14 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-13  1:26 gnu: inetutils: Update to 2.4 Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 15:52 ` Maxim Cournoyer
2023-03-14 16:37   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-14 19:49     ` Andreas Enge [this message]
2023-03-15  1:10     ` Maxim Cournoyer
2023-03-15  2:49       ` Leo Famulari
2023-03-15  3:30         ` Branch and release process (was: gnu: inetutils: Update to 2.4.) Maxim Cournoyer
2023-03-15 11:37           ` Efraim Flashner
2023-03-15 13:32             ` Branch and release process Maxim Cournoyer
2023-03-15 13:37               ` Andreas Enge
2023-03-15 11:56           ` Branch and release process (was: gnu: inetutils: Update to 2.4.) Leo Famulari
2023-03-15 12:04             ` Christopher Baines
2023-03-15  7:48       ` gnu: inetutils: Update to 2.4 Andreas Enge
2023-03-15 13:37         ` Maxim Cournoyer
2023-03-16 20:43       ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-03-17 16:32         ` Maxim Cournoyer

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=ZBDPr71maZqhszLT@jurong \
    --to=andreas@enge.fr \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.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).