Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org,
	James Hilliard <james.hilliard1@gmail.com>,
	 Marcus Hoffmann <bubu@bubu1.eu>
Subject: Re: [Buildroot] [PATCH v5] package/python-diskcache: new package
Date: Mon, 2 Feb 2026 17:44:35 +0100	[thread overview]
Message-ID: <aYDUUf6FTJtgvb3J@windsurf> (raw)
In-Reply-To: <20251021120548.1534100-1-buildroot@bubu1.eu>

On Tue, Oct 21, 2025 at 02:05:47PM +0200, Marcus Hoffmann via buildroot wrote:
> The package imports itself in setup.py to get the package-name and
> version number. Dping this during the buildroot build would require
> buisling host-python with sqlite support, which we are currently not set
> up for. It also seems wasteful for just extracting the version number
> and package name, so instead we replace the import by using a hardcoded
> package-name and the version number stored in buildroot.
> 
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>

Thanks a lot, applied! I only adjusted indentation in the .mk file and
added a comment above the hook to explain what's going on.

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-02-02 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 12:05 [Buildroot] [PATCH v5] package/python-diskcache: new package Marcus Hoffmann via buildroot
2026-02-02 16:44 ` Thomas Petazzoni via buildroot [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=aYDUUf6FTJtgvb3J@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bubu@bubu1.eu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox