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 1E2F213838B for ; Tue, 9 Sep 2014 15:21:45 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B3411E0852; Tue, 9 Sep 2014 15:21:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7A87FE082F for ; Tue, 9 Sep 2014 15:21:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 94E3134003D for ; Tue, 9 Sep 2014 15:21:34 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -2.592 X-Spam-Level: X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5.5 tests=[AWL=0.609, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.499, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcZjnmq8nyCC for ; Tue, 9 Sep 2014 15:21:28 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id A2DB1340030 for ; Tue, 9 Sep 2014 15:21:28 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XRNEH-0004sU-Gl for gentoo-user@gentoo.org; Tue, 09 Sep 2014 17:21:13 +0200 Received: from rrcs-71-40-157-251.se.biz.rr.com ([71.40.157.251]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Sep 2014 17:21:13 +0200 Received: from wireless by rrcs-71-40-157-251.se.biz.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Sep 2014 17:21:13 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: James Subject: [gentoo-user] post build files Date: Tue, 9 Sep 2014 15:20:26 +0000 (UTC) Message-ID: 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 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 71.40.157.251 (Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26.1) X-Archives-Salt: 70130d73-8a0b-46c7-b678-18b479f83df3 X-Archives-Hash: 790e2af4ec51f5a45370ccade31013c3 Hello, I'm rather new to hacking ebuilds. I have read most every doc I can find on the subject. One thing I'm looking for is a post-build document that shows me the path/name of everything built. So for mesos-0.20.0 it seems to be: /var/db/pkg/sys-cluster/mesos-0.20.0/CONTENTS For some other packages, they seems to be quit a lot under /var/tmp/portage/ Some of the information I'm looking for is in /var/log/elog/ Other places to look? Mesos generates a lot of *.html file that I'm speculating are general purpose setup interfaces for configuring and controlling the various code components. It this typical of Apache codes? I feel like I'm missing the 'big picture' on where one looks to find all these files that some packages generate. On new software, I guess I have to look at them all to figure out a runtime environment setup? I feel linke I'm on Safari (an actual dangerous animal hunting trip) but there has been no briefing. I feel hung_over, naked and without compass. I feel like I need a bottle of whisky to just start "winging it"...... Understand what I'm doing: I have stable tree ebuilds, Overlays of various quality and then there are my ebuilds (ugly hacks) in /usr/local/portage that I'm trying to get my arms around with a weak comprehension of what to expect. I also have read about Blueness efforts: "RFC: GLEP 64: Standardize contents of VDB" on the dev list and that just leaves me scratching (more than my head). Some discussion, suggested reading, and guidance would be welcome as the structure(s) seem a wee bit "loose" if not inconsistent, to me...... How much does EAPI- affect what a package build does? Where do I have I go before compiling code (typically) in the unpacked sourcecode to see/determine what is going to get build and where it will install, as this is not strictly controlled by the ebuilds...... How much is controlled by the package codes and how much by setting in the Gentoo build settings? Most of the docs I've read, would make sense, if I knew what I was specifically suppose to do. Learning the semantics of all of this "echo_system" does not seem straightforward. The individual codes are not the problem, as I can read and discern most codes. It's the WISDOM of what goes WHERE and WHY that seems; fleeting to me. lost & curious, James