From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH RFC 1/1] Config.in: remove experimental status of per-package SDK and target
Date: Fri, 2 Jan 2026 23:25:27 +0100 [thread overview]
Message-ID: <20260102232527.0d0779b2@windsurf> (raw)
In-Reply-To: <20260102222022.3464952-1-bernd@kuhls.net>
Hello Bernd,
On Fri, 2 Jan 2026 23:20:22 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:
> The last buildroot commit mentioning "per-pack" dates back to 2024:
>
> $ LC_ALL=C git log --graph --pretty=format:'%h - %d %s (%cr) <%an>' --abbrev-commit -- | grep per-pack | head -n 1
> * aa3ba97554 - package/mender-grubenv: Fix per-package building (1 year, 3 months ago) <Adam Duskett>
>
> so it should be safe to say that enabling BR2_PER_PACKAGE_DIRECTORIES
> is not considered experimental anymore.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
There are actually a few things that are still broken. For example
"make <foo>-reconfigure", "make <foo>-rebuild" and "make
<foo>-reinstall" are broken with per-package directories.
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
prev parent reply other threads:[~2026-01-02 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 22:20 [Buildroot] [PATCH RFC 1/1] Config.in: remove experimental status of per-package SDK and target Bernd Kuhls
2026-01-02 22:25 ` 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=20260102232527.0d0779b2@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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.