From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 680 invoked by uid 1002); 3 Oct 2003 09:52:52 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28067 invoked from network); 3 Oct 2003 09:52:52 -0000 Message-ID: <3F7D4741.40603@gentoo.org> Date: Fri, 03 Oct 2003 05:54:09 -0400 From: Brad Laue User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030925 X-Accept-Language: en-us, en MIME-Version: 1.0 To: gentoo-dev@gentoo.org References: <3F7D4315.1020900@gentoo.org> In-Reply-To: <3F7D4315.1020900@gentoo.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] Speaking of new kernels being added to the tree X-Archives-Salt: 96c46bda-300c-4c96-95f8-c3ca864eb2f3 X-Archives-Hash: 9235460588b13185418b93c880cfbb59 Just to clarify the above with regard to xfs-sources, wolk-sources et al, rob in #gentoo-dev suggested that a wolk USE flag would collide with a number of gentoo-sources patches. These USE flags would be architected in such a way that enabling 'wolk' would work around such conflicts. Many ebuilds do this; if a USE flag enables a feature with which another feature conflicts, the other feature must be disabled to compensate - shouldn't be much of a logistical problem. Hope that clears that issue up, Brad -- gentoo-dev@gentoo.org mailing list