Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Gantois via buildroot <buildroot@buildroot.org>
To: Buildroot List <buildroot@buildroot.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 11/11] package/snagboot: new package
Date: Mon, 20 Oct 2025 09:17:49 +0200	[thread overview]
Message-ID: <22876007.EfDdHjke4D@fw-rgant> (raw)
In-Reply-To: <20251018194314.114284-12-thomas.petazzoni@bootlin.com>


[-- Attachment #1.1: Type: text/plain, Size: 526 bytes --]

Hi Thomas,

On Saturday, 18 October 2025 21:43:09 CEST Thomas Petazzoni wrote:
> This commit adds a package for Snagboot, the open-source
...

> +
> +# We do not install the dependencies for the snagfactory GUI
> +define SNAGBOOT_REMOVE_SNAGFACTORY
> +	$(RM) $(HOST_DIR)/bin/snagfactory
> +endef

Only the "gui" variant of the Snagboot package provides Snagfactory, the base 
version doesn't, so is this removal really necessary?

Thanks!

-- 
Romain Gantois, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-10-20  7:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 19:42 [Buildroot] [PATCH 00/11] Add support for building Snagboot Thomas Petazzoni via buildroot
2025-10-18 19:42 ` [Buildroot] [PATCH 01/11] support/testing/infra: improve run_cmd_on_host() to show stdout/stderr Thomas Petazzoni via buildroot
2025-10-30 21:03   ` Julien Olivain via buildroot
2025-11-17 19:56   ` Arnout Vandecappelle via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 02/11] support/testing/infra/basetest.py: add BRHostPkgTest class Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 03/11] package/python-crccheck: new package Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 04/11] support/testing/tests/package/test_python_serial.py: new test case Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 05/11] package/python-tftpy: add host variant Thomas Petazzoni via buildroot
2025-10-20 15:18   ` Colin Foster
2025-10-18 19:43 ` [Buildroot] [PATCH 06/11] package/python-pyusb: enable " Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 07/11] package/python-xmodem: add " Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 08/11] package/python-appdirs: " Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 09/11] package/python-fs: new package Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 10/11] package/python-pyfatfs: " Thomas Petazzoni via buildroot
2025-10-18 19:43 ` [Buildroot] [PATCH 11/11] package/snagboot: " Thomas Petazzoni via buildroot
2025-10-20  7:17   ` Romain Gantois via buildroot [this message]
2025-10-20  7:54     ` Thomas Petazzoni via buildroot
2025-10-29  8:13       ` Romain Gantois 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=22876007.EfDdHjke4D@fw-rgant \
    --to=buildroot@buildroot.org \
    --cc=romain.gantois@bootlin.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