lkml.org 
[lkml]   [2012]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] kconfig: untangle EXPERT and EMBEDDED
On Tue, Jan 17, 2012 at 12:46:01PM -0800, David Rientjes wrote:
> On Tue, 17 Jan 2012, Andrew Jones wrote:
>
> > Now changing it, i.e. making it conform more closely to its name and only
> > affect embedded related options, you can't do. If you were to do so, then
> > you would lose backward compatibility. How do you know there aren't users
> > that started using EMBEDDED for the non-embedded side effects?
>
> That's why they're now using EXPERT.

How do you know they've all switched?

>
> > If EMBEDDED
> > is ever corrected, and then stops selecting EXPERT, then you risk causing
> > them problems.
> >
>
> No, because they've already enabled EXPERT. You can't have EMBEDDED=y and
> EXPERT=n. That's what this little thing called "select" does. After a
> sufficient amount of time passes and all options that are important only
> for embedded users have been either extended for EMBEDDED or replaced only
> be EMBEDDED, you can get rid of the "select" without losing backwards
> compatibility.

How do you define a sufficient amount of time? How do you know everyone
else agrees with that definition? OIOW, where is it documented? If it is
documented, then how do you know everyone will read it and comply to it?

Those are rhetorical questions. Please don't try to answer them. You'd
only embarrass yourself further.


\
 
 \ /
  Last update: 2012-01-18 09:19    [W:0.164 / U:0.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site