From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263188AbVGaAuP (ORCPT ); Sat, 30 Jul 2005 20:50:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263198AbVGaAuP (ORCPT ); Sat, 30 Jul 2005 20:50:15 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:41443 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S263188AbVGaAuM (ORCPT ); Sat, 30 Jul 2005 20:50:12 -0400 Date: Sun, 31 Jul 2005 02:50:03 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Sam Ravnborg cc: kbuild-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Subject: Re: [RFD] kconfig - introduce cond-source In-Reply-To: <20050730220100.GA3240@mars.ravnborg.org> Message-ID: References: <20050730220100.GA3240@mars.ravnborg.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Sun, 31 Jul 2005, Sam Ravnborg wrote: > In a couple of cases I have had the need to include a Kconfig file only > if present. > The current 'source' directive works as one would expect. It bails out > if the file is missing. I don't really like it, it's an open invitation to abuse. I'd rather like to see the user first, which might need it. bye, Roman