From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 6441E1381F3 for ; Wed, 10 Apr 2013 17:35:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 04B80E0A6D; Wed, 10 Apr 2013 17:35:28 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7239AE0A6D for ; Wed, 10 Apr 2013 17:35:27 +0000 (UTC) Received: from mail-qe0-f43.google.com (mail-qe0-f43.google.com [209.85.128.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mattst88) by smtp.gentoo.org (Postfix) with ESMTPSA id 49C0C33DC6D for ; Wed, 10 Apr 2013 17:35:26 +0000 (UTC) Received: by mail-qe0-f43.google.com with SMTP id f6so400451qej.2 for ; Wed, 10 Apr 2013 10:35:24 -0700 (PDT) X-Received: by 10.49.2.7 with SMTP id 7mr3636504qeq.45.1365615324495; Wed, 10 Apr 2013 10:35:24 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.49.35.37 with HTTP; Wed, 10 Apr 2013 10:35:04 -0700 (PDT) In-Reply-To: <51658B47.3020008@arskom.com.tr> References: <51658B47.3020008@arskom.com.tr> From: Matt Turner Date: Wed, 10 Apr 2013 10:35:04 -0700 Message-ID: Subject: Re: [gentoo-catalyst] make catalyst call emerge --deep To: gentoo-catalyst@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: edd8e318-bd01-485c-9fec-2ce82f88bd1c X-Archives-Hash: e2df6eb7a2318fd144e02b3a9a72f461 On Wed, Apr 10, 2013 at 8:54 AM, Burak Arslan wrote: > Hi, > > In a build (a desktop stage 4) I'm trying to run, I'm getting multiple udevs > (=197-r1 and >=197-r2) pulled in (among other errors, see below). My > impression is that if I were able to pass --deep to emerge command, it'd > just go through. Is there a non-hacky way of doing this? Modify catalyst and try it. We should confirm that --deep actually would fix this problem before deciding it's the solution. If it is, I'm all for adding it.