unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Status of ‘core-updates’
Date: Wed, 10 Apr 2024 16:39:40 +0200	[thread overview]
Message-ID: <874jc9l1sj.fsf@gnu.org> (raw)
In-Reply-To: <87h6got2e0.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sat,  30 Mar 2024 11:55:35 +0100")

Hello!

Josselin Poiret <dev@jpoiret.xyz> skribis:

> Disclaimer: I've been quite busy with work recently and haven't been
> able to work on core-updates that much (having to build the world
> locally doesn't help).

No problem.  We should find someone willing to pick up the coordination
work for the coming month or so.  Any volunteer?  :-)

To be clear (but I guess it’s crystal clear to anyone who’s been around
long enough :-)), what we need most is someone to keep track of changes,
coordinate efforts, decide what goes in the branch and what’s postponed
or moved to a separate branch, and send periodic (weekly) status updates
over the course of a couple of months.  This can (and probably should)
be done without doing any actual hacking on the branch.

> Currently, the desktop system image doesn't build anymore because we've
> also integrated patches to use pkgconf instead of pkg-config.  I think
> the effort to actually make that work with all of our packages is going
> to be a bit too much to handle right now.  IMO, we should probably
> revert/branch out before then so that we can push core-updates past the
> finish line.  A feature branch to integrate pkgconf properly could then
> be worked on later.

Last time we discussed it on IRC, you were in the process of putting up
a branch without those pkgconf changes, IIRC.  Were you able to complete
that work?

If not, I guess that’ll be the first thing to do, unless someone has a
better idea.

> Other than that, I was able to get a working desktop before the
> aforementioned patches but with some locale errors that I fixed with
> ae07bc2dd0124b625acf70e594ccc90d6d128562, so I'm not expecting too much
> trouble.  We'll probably have to add libxcrypt as an input to some other
> packages that I haven't tested yet, but that's quite trivial.

Alright.

Thanks for all the work so far!

Ludo’.


  reply	other threads:[~2024-04-10 14:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-24 11:21 Status of ‘core-updates’ Ludovic Courtès
2024-03-30 10:55 ` Josselin Poiret
2024-04-10 14:39   ` Ludovic Courtès [this message]
2024-04-11 10:18     ` Steve George
2024-04-12 20:21       ` Ludovic Courtès
2024-04-17 17:47         ` Maxim Cournoyer
2024-04-17 22:52           ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-04-19 14:13           ` Ludovic Courtès
2024-04-19 15:22             ` Maxim Cournoyer
2024-04-22 16:20           ` Efraim Flashner
2024-04-20 11:14 ` Christopher Baines
2024-04-20 21:15   ` Maxim Cournoyer
2024-05-02  7:53   ` bug#70456: Request for merging "core-updates" branch 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=874jc9l1sj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dev@jpoiret.xyz \
    --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).