v2025.10 env Kconfig rename (fb5235239aad) removed backward compatibility

[Philip Molloy]

Hi Quentin,

Thanks for the quick reply and patch submission to Buildroot. I'll leave that discussion to the Buildroot mailing list.

On Monday, November 24th, 2025 at 1:32 PM, Quentin Schulz <quentin.schulz at cherry.de> wrote:
> On 11/22/25 2:18 PM, Ozan Durgut wrote:
> 
> > [You don't often get email from ozandurgut.2001 at hotmail.com. Learn why
> > this is important at https://aka.ms/LearnAboutSenderIdentification ]
> > 
> > Dear U-Boot maintainers,
> > 
> > I hope you're doing well.
> > 
> > I would like to raise a backward compatibility concern regarding commit
> > fb5235239aad ("env: Rename DEFAULT_ENV_FILE to
> > ENV_DEFAULT_ENV_TEXT_FILE"), which landed in the v2025.10 release.
> 
> I don't think we ever advertised backward compatibility for Kconfig
> symbols/defconfig.

Is this clearly documented and communicated to users such that the vast majority would expect this functionality? How does this work in other projects that use kconfig like the Kernel and Buildroot, among others? If there are differences why have they taken that approach?

As Ozan said in his e-mail he is open to collaborating on a solution.

Best,
Philip