From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Michael Walle <michael@walle.cc>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH RESEND 1/2] package/urandom-scripts: move to new package busybox-initscripts
Date: Mon, 13 Mar 2023 09:21:31 +0100 [thread overview]
Message-ID: <20230313092131.04406301@windsurf> (raw)
In-Reply-To: <20230313081549.493823-2-michael@walle.cc>
On Mon, 13 Mar 2023 09:15:48 +0100
Michael Walle <michael@walle.cc> wrote:
> +config BR2_PACKAGE_URANDOM_SCRIPTS
> + bool "urandom-initscripts package was renamed"
> + select BR2_LEGACY
> + select BR2_PACKAGE_BUILDROOT_INITSCRIPTS
> + select BR2_PACKAGE_BUILDROOT_INITSCRIPTS_URANDOM
This is basically causing to cause the legacy warning to trigger for
virtually all configurations, as this package is enabled in basically
all non-systemd configurations.
It's a bit annoying :-/
One option would be to not have the "select BR2_LEGACY", which would
work OK because of the 2 selects that enable the new package. But
it would also mean that people will keep BR2_PACKAGE_URANDOM_SCRIPTS=y
in their .config forever.
I don't really have a good solution/idea here, just pointing out this
inconvenience.
Best regards,
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
next prev parent reply other threads:[~2023-03-13 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 8:15 [Buildroot] [PATCH RESEND 0/2] new package buildroot-initscripts Michael Walle via buildroot
2023-03-13 8:15 ` [Buildroot] [PATCH RESEND 1/2] package/urandom-scripts: move to new package busybox-initscripts Michael Walle via buildroot
2023-03-13 8:21 ` Thomas Petazzoni via buildroot [this message]
2025-05-18 20:46 ` Arnout Vandecappelle via buildroot
2023-03-13 8:15 ` [Buildroot] [PATCH RESEND 2/2] package/buildroot-initscripts: add hwclock initscript Michael Walle via buildroot
2025-05-18 20:47 ` 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=20230313092131.04406301@windsurf \
--to=buildroot@buildroot.org \
--cc=michael@walle.cc \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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.