From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Nnr7K-0000J5-JR for garchives@archives.gentoo.org; Sat, 06 Mar 2010 10:20:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CFE92E0875; Sat, 6 Mar 2010 10:19:19 +0000 (UTC) Received: from qw-out-1920.google.com (qw-out-1920.google.com [74.125.92.149]) by pigeon.gentoo.org (Postfix) with ESMTP id A4F89E0875 for ; Sat, 6 Mar 2010 10:19:19 +0000 (UTC) Received: by qw-out-1920.google.com with SMTP id 14so401969qwa.10 for ; Sat, 06 Mar 2010 02:19:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=QFsivj0ZMhcbYMwMHC/I4wl0uKyZb2T2LHU62sn5lAo=; b=lVYq8F+0h2adkUjeMARTz5ASw6DgkJGZyUzWNWyn4F7NH0nAaeJgz3GEPBrSg+hRLQ eeGw4Ha9yXjmqJkC6btPDTDCsUMVUmjKLoS8stkfptMmXNkZImqbI7A7A1YMyQ7e6eNV VMTZ6OXHm9kWPzi9fVctcPdzAdupKBLB2ElCk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=PlbINqKdAiptz5Hsn69QgqcTAwQhO3LNskK3965G6xsK3EZBsk5yq9tDugwVq5hBuk 5ZffgdQGt5naf2Ooc2TCYlmVkcFLhI/d10QdWM4HvdZ8vk4Mj9yqSC42nha5dnyJ0SZV OU+WxgQ8hRgwPXqS8uzRAkPK1y9yRX7zo7cuM= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.229.218.204 with SMTP id hr12mr999169qcb.101.1267870759315; Sat, 06 Mar 2010 02:19:19 -0800 (PST) Date: Sat, 6 Mar 2010 18:19:19 +0800 Message-ID: <6e2210231003060219u69cba62dle9b8c0c4a4661364@mail.gmail.com> Subject: [gentoo-user] Any nice tools for emerge dependency resolution listing? From: Mark David Dumlao To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: a909032d-d782-42b7-a045-a65892cf5893 X-Archives-Hash: 9b5fc752c59814bd94dcff27c8d406d5 Hi! I'm wondering if anyone's written a script that looks deep into the build dependencies of some package foo, and gives you a list of ebuilds you need to unmask to build it. Immediate build dependencies could easily be shown using the ebuild itself, and deep dependencies could be shown using equery something, but I just want to focus on dependencies you need to unmask when building. I usually just manually iterate through emerge -uDNtav world/something to make something like that happen, and it's just hit me that this sounds like a chore that's bound to have bugged someone. I'm not looking for a tool that writes my package.keywords/* for me, I'd like to do that myself, but the iteration process is more painful than it should be "manually". If there's none I was wondering what kinds of challenges would it take to write one in python as that sounds like a cool exercise to try out. -- This email is: [ ] actionable [ ] fyi [x] social Response needed: [ ] yes [x] up to you [ ] no Time-sensitive: [ ] immediate [ ] soon [x] none