From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4bWZyK55qRz2xWj for ; Tue, 1 Jul 2025 07:52:57 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (secp384r1) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R11" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4bWZyG1CVfz2xGG for ; Tue, 1 Jul 2025 07:52:54 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4bWZyF024sz91; Tue, 1 Jul 2025 07:52:52 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1751356373; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n+umaqv+v3wsoIEYpLT2ls9KzrgpwtqJ2vx0P69rnzM=; b=ROVGo7hHB3DDfiqPiI/JueCBLFJQikXEYvGxOhi5f/Fgoz1JLiZnXCfChNFhsyZAHIgbnv XoF16NXVlwTt5ZAw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1751356373; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n+umaqv+v3wsoIEYpLT2ls9KzrgpwtqJ2vx0P69rnzM=; b=QivSbZavJONo7BDqe2Y46gHBpdjueT7rD1xDPxxiTadWby4GSsRMz2fBlxXHD5D6Kv0QhK OnJ5+1cyorq8jTCg3Z8sjGGDidXhhzrDUjJZNcb/Gm084Wz+mP5s6PDqPfjytKvgc12PXu dk1t28STnvbrtV/2Ritvyso9vl5sTfoa5TF5uTLX9PsKgUiIe0OEA7svQAE+DgDsRCsyzu gtrPAG4d4j2eYAraCBL9c6jLJ+fMvODTSgHtSop4kthvZDzCkC/lQVGh549MfloNFtPm+C EcUTZ+ibexfkkVzUjwpL3CVyAWBPLHJKID5SYYSTYBSJMz5OWP7d2hVlpE+Mkg== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: [PATCH] libusb: Add comment to update nut when libusb is updated From: Michael Tremer In-Reply-To: <20250630161202.3330224-1-adolf.belka@ipfire.org> Date: Tue, 1 Jul 2025 08:52:52 +0100 Cc: development@lists.ipfire.org Content-Transfer-Encoding: quoted-printable Message-Id: <27B2901F-737B-4D2B-B976-D6403754D102@ipfire.org> References: <20250630161202.3330224-1-adolf.belka@ipfire.org> To: Adolf Belka Hello Adolf, Could you tell us my about why this is necessary? The library should have a stable ABI so whenever they are being compiled = independently from each other, they should still work. Best, -Michael > On 30 Jun 2025, at 17:12, Adolf Belka wrote: >=20 > - libusb is a run time requirement for nut >=20 > Signed-off-by: Adolf Belka > --- > lfs/libusb | 1 + > 1 file changed, 1 insertion(+) >=20 > diff --git a/lfs/libusb b/lfs/libusb > index 4b12242d7..0ff89ff75 100644 > --- a/lfs/libusb > +++ b/lfs/libusb > @@ -25,6 +25,7 @@ > include Config >=20 > VER =3D 1.0.29 > +# Ship nut when libusb is updated >=20 > THISAPP =3D libusb-$(VER) > DL_FILE =3D $(THISAPP).tar.bz2 > --=20 > 2.50.0 >=20 >=20