Bug 44540 – Distcc variable mismatch on /etc/make.conf.example

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ben Dugdale 2004-03-13 00:28:53 UTC]

When configuring distcc I noticed that although $DISTCC_DIR was intended to be a subdirectory of $PORTAGE_TMPDIR it actually wound up in my root-directory because its parent $PORT_TMPDIR was null.  $DISTCC_DIR should be a subdirectory of $PORTAGE_TMPDIR which had been set earlier in the file.

ben etc $ grep _TMPDIR make.conf.example 
# PORTAGE_TMPDIR is the location portage will use for compilations and
#PORTAGE_TMPDIR=/var/tmp
#     user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
#DISTCC_DIR="${PORT_TMPDIR}/.distcc"

Here is the header from the make.conf.example

ben etc $ head make.conf.example 
# Copyright 2000-2003 Daniel Robbins, Gentoo Technologies, Inc.
# Contains local system settings for Portage system
# $Header: /home/cvsroot/gentoo-src/portage/cnf/make.conf,v 1.70 2004/01/12 07:34:38 carpaski Exp $

[Comment 1 Markus Nigbur (RETIRED) 2004-03-13 05:56:12 UTC]

--- make.conf.example   2004-02-24 10:59:48.000000000 +0100
+++ make.conf.example_  2004-03-13 14:54:30.639135408 +0100
@@ -283,7 +283,7 @@
 #CCACHE_SIZE="2G"
 #
 # DISTCC_DIR sets the temporary space used by distcc.
-#DISTCC_DIR="${PORT_TMPDIR}/.distcc"
+#DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
 #
 # RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
 #     the portage tree. Specific chucks of the tree may be excluded from

[Comment 2 Lisa Seelye (RETIRED) 2004-03-13 09:32:38 UTC]

dev-portage: This can be completely removed.

Back in 2.0.49-r6 there was a patch applied to the Portage source to define DISTCC_DIR automatically.  But if someone needs to reset it, then who knows.

I've actually just checked a system that was installed in late December, and I think that _this_ bug can be closed, since I can find no record of DISTCC_DIR=portage_tmpdir or anything like that.

[Comment 3 Ben Dugdale 2004-03-13 10:31:18 UTC]

I erroniously put this on 2004.1 but the system is actually 2004.0

According to the information provided by Markus, the appropriate changes have already been made in /etc/make.conf.example dated 2004-03-13 14:54:30.639135408 +0100.  (if I'm correctly reading his comment as a diff).

[Comment 4 werner maier 2004-06-04 14:22:11 UTC]

*** Bug 53007 has been marked as a duplicate of this bug. ***

[Comment 5 Alec Warner (RETIRED) 2005-07-28 21:30:29 UTC]

*** Bug 41697 has been marked as a duplicate of this bug. ***