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 08E7B1393F1 for ; Wed, 16 Sep 2015 13:46:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7198F21C002; Wed, 16 Sep 2015 13:46:44 +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 pigeon.gentoo.org (Postfix) with ESMTPS id 483F9E0863 for ; Wed, 16 Sep 2015 13:46:43 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZcD2f-0005Mk-Pr for gentoo-user@lists.gentoo.org; Wed, 16 Sep 2015 15:46:35 +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 ; Wed, 16 Sep 2015 15:46:33 +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 ; Wed, 16 Sep 2015 15:46:33 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: james Subject: [gentoo-user] Re: portage directory ownerships? Date: Wed, 16 Sep 2015 13:46:23 +0000 (UTC) Message-ID: References: <55F87EAB.20101@gmail.com> <20150916085740.0a7cb2a3@digimed.co.uk> 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:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1) X-Archives-Salt: cdd6ef2f-2247-4e6f-b104-393e62a034e9 X-Archives-Hash: 95753a114e27f0f6955b948d5ea00bac Neil Bothwick digimed.co.uk> writes: > > Here, all of /etc/portage is root:root > > The tree and all overlays are portage:portage > Just to add some confusion to the mix Good example and it got me thinking.... > So some are portage:portage, some are root:root - all use /var/portage > for $PORTDIR so that's not an issue. One of the portage:portage ones is > the one that syncs with the mirrors and acts as an rsync host for the > others, this may or may not be significant. I might swith to /var/portage on a new install. Whats the pedantic reasons for for it? On an SSD for speed ? tmpdir? I'm curious, so tell me more. 1. So 'the tree' (/usr/portage/) is portage:portage OK. 2. and /etc/portages is root:root except for distfiles (root:portage) OK. 3. and /var/lib/layman and subdirs are root:root ??? Note, these are the overlays I use but do not hack on. 4. and /usr/local/portage is james:james this where I hack on codes that are mostly other overlays that need enhancements or raw codes I am processing into ebuilds. 5. /usr/local/experimental is james:james where I working on codes that can compile install or be removed without the baggage of portage/ebuilds. It will be for embedded and cluster/cloud/vm movements of binaries to attach directly to the 4.x kernel, dynamically. I'm working on a new build semantic with DAGs, Tup, ninja and CheckInstall So I can ignore (5) in make.conf. But I'm now getting ebuilds installed in /usr/local/portage, I think because of this line in my make.conf:: PORTDIR_OVERLAY="source /etc/portage/repos.conf/layman.conf" PORTDIR_OVERLAY="/usr/local/portage" For goals of 1-5 what are improvements (any and all suggestions) on make.conf I should make? I need to ensure that overlays that I do not modify stay separate for the ebuild I modify. In fact some packages are in both 3 and 4. I use git to seed category 4 so what caveates do I use to ensure that git only seeds categroy 4 packages (ebuilds)once and does not contaminant my 'old school; vim' hackery. I think this is the only change I need:: PORTDIR_OVERLAY="/usr/local/portage" ==> PORTDIR_OVERLAY="/var/lib/layman" Or does layman and git (syncs) know where to place things. I do use 'git clone' to seed category 4 packages-->ebuilds and will eventually be use more of git's features to push out updates. I just gotta get this straight, consistent and keep things seperate in my mind, because being an old fart, reading lots of codes, sometimes I forget the origins of hacks. (yea yea document the code you old hack) All suggestions welcome. TIA, James