unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
	"Efraim Flashner" <efraim@flashner.co.il>,
	"Steve George" <steve@futurile.net>,
	Kaelyn <kaelyn.alexi@protonmail.com>,
	guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: Core updates status
Date: Wed, 8 May 2024 12:05:19 +0200	[thread overview]
Message-ID: <ZjtOXwyqOZ95099i@jurong> (raw)
In-Reply-To: <87v83r499q.fsf@jpoiret.xyz>

Hello,

Am Mon, May 06, 2024 at 10:47:13AM +0200 schrieb Josselin Poiret:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> > I don't mind too much; when we re-enable the change we should add a
> > phase to the gnu-build-system automatically deleting/moving the libtool
> > archives. so that we're covered.
> 
> I agree, although we'll have to be careful since some packages might
> need them if they don't use pkg-config!

I am a little bit confused by the suggestion; you mean removing all .la
files from all packages? I thought they were there for a reason, and
usually recorded the dependencies. For instance, doing a "guix build mpc"
and looking at libmpc.la, my impression is that I see correct information.
Why would one want to force upstream to add a pkgconfig dependency
additionally to libtool? Or do I misunderstand the suggestion?

Andreas



  parent reply	other threads:[~2024-05-08 10:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  6:08 Core updates status Steve George
2024-04-24  9:56 ` Christina O'Donnell
2024-04-24 13:17   ` Steve George
2024-04-24 14:21     ` Christina O'Donnell
2024-04-25 14:06     ` Christina O'Donnell
2024-04-25 14:06       ` bug#40316: " Christina O'Donnell
2024-04-25 17:01       ` nss not reproducible Christina O'Donnell
2024-04-25 18:45 ` Core updates status Kaelyn
2024-04-26 12:56   ` Steve George
2024-04-26 15:58     ` Efraim Flashner
2024-05-05 20:45       ` Josselin Poiret
2024-05-06  2:38         ` Maxim Cournoyer
2024-05-06  8:47           ` Josselin Poiret
2024-05-06 10:21             ` Ludovic Courtès
2024-05-08  9:03               ` Josselin Poiret
2024-05-08 21:42                 ` [PATCH] gnu: glibc: Update patches following upstream's master branch Josselin Poiret
2024-05-14  9:22                   ` Ludovic Courtès
2024-05-09 15:41                 ` Core updates status Maxim Cournoyer
2024-05-13  8:49                 ` Efraim Flashner
2024-05-08 10:05             ` Andreas Enge [this message]
2024-05-08 17:46               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-05-09 15:38               ` Maxim Cournoyer
2024-05-10  8:08                 ` Andreas Enge
2024-05-13  8:51                 ` Efraim Flashner

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=ZjtOXwyqOZ95099i@jurong \
    --to=andreas@enge.fr \
    --cc=dev@jpoiret.xyz \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=kaelyn.alexi@protonmail.com \
    --cc=ludo@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=steve@futurile.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).