All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
Cc: Marcus Hoffmann <buildroot@bubu1.eu>,
	Angelo Compagnucci <angelo.compagnucci@gmail.com>,
	James Hilliard <james.hilliard1@gmail.com>
Subject: Re: [Buildroot] [PATCH] package/python-can: remove msgpack dependency
Date: Sat, 27 Dec 2025 16:57:39 +0100	[thread overview]
Message-ID: <20251227165739.031d2a96@windsurf> (raw)
In-Reply-To: <20251204190609.3846747-1-buildroot@bubu1.eu>

On Thu,  4 Dec 2025 20:06:09 +0100
Marcus Hoffmann via buildroot <buildroot@buildroot.org> wrote:

> Dependency was made optional in 4.6.0 release here:
> https://github.com/hardbyte/python-can/commit/6058ab9dfe8b3ba5d23cbff670c0fe767147390a
> 
> python-can has a lot of optional dependencies, most of which are not
> represented in buildroot. As msgpack is used for the virtual multicast
> udp can interface[1], which does seem like a bit of a niche usecase,
> just drop the mandatory dependency without introducing a user-visible
> config option to enable it.
> 
> [1] https://python-can.readthedocs.io/en/4.0.0/interfaces/udp_multicast.html
> 
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
> ---
>  package/python-can/Config.in | 1 -
>  1 file changed, 1 deletion(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-12-27 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 19:06 [Buildroot] [PATCH] package/python-can: remove msgpack dependency Marcus Hoffmann via buildroot
2025-12-27 15:57 ` Thomas Petazzoni via buildroot [this message]
2026-01-07 17:55 ` Arnout Vandecappelle via buildroot

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251227165739.031d2a96@windsurf \
    --to=buildroot@buildroot.org \
    --cc=angelo.compagnucci@gmail.com \
    --cc=buildroot@bubu1.eu \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.