Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [Feature request] Find all non-existent config options by CI/CD
@ 2024-10-29  6:38 CHERNIAEV ANDREI
  2024-10-29 11:19 ` Thomas Petazzoni via buildroot
  0 siblings, 1 reply; 4+ messages in thread
From: CHERNIAEV ANDREI @ 2024-10-29  6:38 UTC (permalink / raw)
  To: buildroot


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

As [you know](https://gitlab.com/buildroot.org/buildroot/-/issues/57) buildroot contains some amount of non-existent BR2_ config options. I suggest to discuss should we make script to automatically detect all bad BR2_ and how to integrate it to CI/CD. In my point of view we also should detect legacy config options which are not marked as "legacy".
Why I can't make such script? Because I don't know how to get a list of all non-legacy BR2_ config options

P.S. Let's use https://gitlab.com/buildroot.org/buildroot/-/issues to discuss about new feature!

[-- Attachment #1.2: Type: text/html, Size: 1181 bytes --]

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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Buildroot] [Feature request] Find all non-existent config options by CI/CD
  2024-10-29  6:38 [Buildroot] [Feature request] Find all non-existent config options by CI/CD CHERNIAEV ANDREI
@ 2024-10-29 11:19 ` Thomas Petazzoni via buildroot
  2024-10-29 11:57   ` CHERNIAEV ANDREI
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Petazzoni via buildroot @ 2024-10-29 11:19 UTC (permalink / raw)
  To: CHERNIAEV ANDREI; +Cc: buildroot

Hello Andrei,

On Tue, 29 Oct 2024 15:38:26 +0900
CHERNIAEV ANDREI <dungeonlords789@naver.com> wrote:

> As [you
> know](https://gitlab.com/buildroot.org/buildroot/-/issues/57) buildroot contains some amount of non-existent BR2_ config options. I suggest to discuss should we make script to automatically detect all bad BR2_ and how to integrate it to CI/CD. In my point of view we also should detect legacy config options which are not marked as "legacy".
> Why I can't make such script? Because I don't know how to get a list
> of all non-legacy BR2_ config options
> 
> P.S. Let's
> use https://gitlab.com/buildroot.org/buildroot/-/issues to discuss about new feature!

We already have such a check in check-package, but it checks Config.in
and .mk files, not random documentation indeed.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Buildroot]  [Feature request] Find all non-existent config options by CI/CD
  2024-10-29 11:19 ` Thomas Petazzoni via buildroot
@ 2024-10-29 11:57   ` CHERNIAEV ANDREI
  2024-10-29 16:04     ` Thomas Petazzoni via buildroot
  0 siblings, 1 reply; 4+ messages in thread
From: CHERNIAEV ANDREI @ 2024-10-29 11:57 UTC (permalink / raw)
  To: Thomas Petazzoni; +Cc: buildroot


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

Why you call the officially part of buildroot documentation as "random documentation"? Is file "/support/kconfig/README.buildroot" or "buildroot/blob/master/board/qemu/x86/readme.txt" also "random documentation"? So if any file from buildroot repo is not Config.in or .mk then buildroot doesn't plan to check it?

-----Original Message-----
From: "Thomas Petazzoni via buildroot"<buildroot@buildroot.org>
To: "CHERNIAEV ANDREI"<dungeonlords789@naver.com>;
Cc: <buildroot@buildroot.org>;
Sent: 2024-10-29 (화) 20:19:08 (GMT+09:00)
Subject: Re: [Buildroot] [Feature request] Find all non-existent config options by CI/CD

Hello Andrei,

On Tue, 29 Oct 2024 15:38:26 +0900
CHERNIAEV ANDREI <dungeonlords789@naver.com> wrote:

> As [you
> know](https://gitlab.com/buildroot.org/buildroot/-/issues/57) buildroot contains some amount of non-existent BR2_ config options. I suggest to discuss should we make script to automatically detect all bad BR2_ and how to integrate it to CI/CD. In my point of view we also should detect legacy config options which are not marked as "legacy".
> Why I can't make such script? Because I don't know how to get a list
> of all non-legacy BR2_ config options
>
> P.S. Let's
> use https://gitlab.com/buildroot.org/buildroot/-/issues to discuss about new feature!

We already have such a check in check-package, but it checks Config.in
and .mk files, not random documentation indeed.

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

[-- Attachment #1.2: Type: text/html, Size: 2828 bytes --]

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

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Buildroot] [Feature request] Find all non-existent config options by CI/CD
  2024-10-29 11:57   ` CHERNIAEV ANDREI
@ 2024-10-29 16:04     ` Thomas Petazzoni via buildroot
  0 siblings, 0 replies; 4+ messages in thread
From: Thomas Petazzoni via buildroot @ 2024-10-29 16:04 UTC (permalink / raw)
  To: CHERNIAEV ANDREI; +Cc: buildroot

Hello,

On Tue, 29 Oct 2024 20:57:07 +0900
CHERNIAEV ANDREI <dungeonlords789@naver.com> wrote:

> Why you call the officially part of buildroot documentation as
> "random documentation"? Is file "/support/kconfig/README.buildroot"
> or "buildroot/blob/master/board/qemu/x86/readme.txt" also "random
> documentation"? So if any file from buildroot repo is not Config.in
> or .mk then buildroot doesn't plan to check it?

For now, check-package is only capable of verifying the coding style of
Config.in, .hash files, .mk files. At this point, I don't expect it to
ever be capable of scanning/validating *.txt files, as their content
can be quite arbitrary.

Of course, you are welcome to develop improvements in this area if you
feel like it should be improved.

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-10-29 16:04 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-10-29  6:38 [Buildroot] [Feature request] Find all non-existent config options by CI/CD CHERNIAEV ANDREI
2024-10-29 11:19 ` Thomas Petazzoni via buildroot
2024-10-29 11:57   ` CHERNIAEV ANDREI
2024-10-29 16:04     ` Thomas Petazzoni via buildroot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox