[Buildroot] a philosophical question about Config.in and "comment" directives

Peter Korsgaard peter at korsgaard.com
Mon Apr 20 19:19:40 UTC 2015


>>>>> "Arnout" == Arnout Vandecappelle <arnout at mind.be> writes:

Hi,

 >>> that layout makes it far clearer that the entire option depends on
 >>> arm or you see *nothing* and, further, internally, the dependencies
 >>> in the comment list *only* those dependencies that the user will be
 >>> warned that they need if they want this selection.

 >  I completely agree.

Me too.

 >> So yes, you are right _on principle_. But we're not gonna change that
 >> policy, and we'll continue to require new packages to conform to it.

 >  We _could_ change the policy and just require new packages to conform to the
 > new policy. We do that regularly (cfr. patch naming, BR2_ prefix, ...).

 >  That said, I don't think the current situation is bad enough to
 > warrant such a change.

No indeed. I wouldn't mind new patches doing it like this, but I don't
want to se the churn to change our ~1500 existing packages to it.

-- 
Bye, Peter Korsgaard



More information about the buildroot mailing list