public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Why arch-specific make.conf files?
Date: Wed, 16 Nov 2005 10:47:42 -0700	[thread overview]
Message-ID: <pan.2005.11.16.17.47.41.639638@cox.net> (raw)
In-Reply-To: 20051116160434.629519df@sven.genone.homeip.net

Marius Mauch posted <20051116160434.629519df@sven.genone.homeip.net>,
excerpted below,  on Wed, 16 Nov 2005 16:04:34 +0100:

> You have a list of (some of) these things? From a portage POV those
> things are broken, the only thing you can safely assume about
> make.conf is that it exists (and even that is debatable).

Plus, I'm enthusiastically using the still fairly new "source xyzfile"
functionality in portage to break out my portage config into various
modules (use, fs, net, etc).  My make.conf itself is simply a collection
of several "source" lines.  If whatever is brokenly assuming it can
collect such info from make.conf is sourcing the file using bash, or if it
too understands the source directive, no problem, but if not, it could be
a serious problem!

FWIW, I've experienced no issues here. (I don't use distcc, so that
already mentioned issue doesn't affect me.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-11-16 17:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 19:19 [gentoo-dev] Why arch-specific make.conf files? Marius Mauch
2005-11-15 19:26 ` Diego 'Flameeyes' Pettenò
2005-11-15 19:54   ` Chris Gianelloni
2005-11-16  2:30     ` Marius Mauch
2005-11-16 12:50       ` Chris Gianelloni
2005-11-16 15:04         ` Marius Mauch
2005-11-16 17:47           ` Duncan [this message]
2005-11-15 19:52 ` Chris Gianelloni
2005-11-15 20:01   ` Mike Frysinger
2005-11-15 21:01     ` Chris Gianelloni
2005-11-15 21:12       ` Mike Frysinger
2005-11-16  2:40   ` Marius Mauch
2005-11-15 19:55 ` Chris Gianelloni
2005-11-16 17:18 ` Gustavo Zacarias

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2005.11.16.17.47.41.639638@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox