Hi Aristeu. > > >>> nonint_oldconfig: > > >>> - renamed to listnewconfig > > >>> - print new options to stdout (to better support redirect) > > >>> - no longer saves a new configuration > > >>> - does ot exist with a failure code if there is new options > > > but this kills its usefulness. nonint_oldconfig is used so you can script > > > the use of a generated configuration (think distro kernel RPMs). if something > > > is not set, it fails listing what's not set. otherwise it'll save the > > > configuration and whatever script is using it can proceed. > > > "listnewconfig" is a new, different target to me. If you have a simple command that give you a list of new symbols then this is easy to script as Michal also shows with the below example. > > How about > > new=$(make listnewconfig) > > if test -n "$new"; then > > echo "Please set the following options:" >&2 > > echo "$new" >&2 > > exit 1 > > fi > > ? Wouldn't that be the same as nonint_oldconfig before? > what's the other use cases for listnewconfig (other than a incomplete > nonint_oldconfig)? listnewconfig is for everyone that like to see a list of new config options - without touching the current configuration. By limiting listnewconfig to do only one thing you actually create further uses than before. This is not about how well it applies to the tailored use in redhat's current scripts. This is about creating a command which by doing only a single thing (and to do so well) allows others to utilize this. Sam -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
