Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Flaviu Nistor <flaviu.nistor@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Flaviu Nistor <flaviu.nistor@gmail.com>,
	buildroot@buildroot.org,
	James Hilliard <james.hilliard1@gmail.com>,
	Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH v5 1/2] package/python-snappy: bump version to 0.7.2
Date: Wed, 21 Oct 2026 09:19:20 +0300	[thread overview]
Message-ID: <20261021061921.7401-1-flaviu.nistor@gmail.com> (raw)
In-Reply-To: <atZQYQamSfa5wqAN@windsurf>

On Mon, Oct 19, 2026 at 8:17 PM, Thomas Petazzoni wrote:
>On Fri, Oct 16, 2026 at 03:32:58PM +0300, Flaviu Nistor wrote:
>
>> -PYTHON_SNAPPY_VERSION = 0.6.1
>> -PYTHON_SNAPPY_SITE = https://files.pythonhosted.org/packages/98/7a/44a24bad98335b2c72e4cadcdecf79f50197d1bab9f22f863a274f104b96
>> +PYTHON_SNAPPY_VERSION = 0.7.2
>> +PYTHON_SNAPPY_SOURCE = python_snappy-$(PYTHON_SNAPPY_VERSION).tar.gz
>> +PYTHON_SNAPPY_SITE = https://files.pythonhosted.org/packages/cb/52/acd87583175fa930e4385f8a6164eb5909acd683c0e62ee01d41de8195a2
>>  PYTHON_SNAPPY_SETUP_TYPE = setuptools
>>  PYTHON_SNAPPY_LICENSE = BSD-3-Clause
>>  PYTHON_SNAPPY_LICENSE_FILES = LICENSE
>> -PYTHON_SNAPPY_DEPENDENCIES = snappy
>> +PYTHON_SNAPPY_DEPENDENCIES = host-python-cramjam python-cramjam
>
>It's a bit annoying to pull in host-python-cramjam for no other reason
>than making the dependency check happy. So instead I've changed to use:

Indeed it is annoying and does not make a lot of sense. I could not
find a workaround for the build error, so thank you for your solution.
I did not think of it, but it is nice to learn something now.

Best regards,
Flaviu Nistor
>
>PYTHON_SNAPPY_BUILD_OPTS = --skip-dependency-check
>
>and drop the two dependencies. python-cramjam becomes a pure runtime
>dependency. Verified by running your test in PATCH 2/2.
>
>Applied with this change (and a reworded commit log), thanks!
>
>Thomas
>-- 
>Thomas Petazzoni, co-owner and CEO, Bootlin
>Embedded Linux and Kernel engineering and training
>https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2026-10-21  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 12:32 [Buildroot] [PATCH v5 1/2] package/python-snappy: bump version to 0.7.2 Flaviu Nistor
2026-10-16 12:32 ` [Buildroot] [PATCH v5 2/2] support/testing: add snappy test Flaviu Nistor
2026-10-19 17:17   ` Thomas Petazzoni via buildroot
2026-10-19 17:17 ` [Buildroot] [PATCH v5 1/2] package/python-snappy: bump version to 0.7.2 Thomas Petazzoni via buildroot
2026-10-21  6:19   ` Flaviu Nistor [this message]

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=20261021061921.7401-1-flaviu.nistor@gmail.com \
    --to=flaviu.nistor@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox