public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joel Konkle-Parker <jjk3@msstate.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: a suggestion about einfo messages
Date: Fri, 23 Jul 2004 07:32:05 -0400	[thread overview]
Message-ID: <cdqsvl$r5q$1@sea.gmane.org> (raw)
In-Reply-To: <4100D576.80609@gentoo.org>

Kumba wrote:
> A small (IMHO) bug in catalsyt (the utility that builds stages) 
> generates its own make.conf file, and I think after building, it should 
> copy over a full portage make.conf for users, as the catalyst generated 
> one lacks comments and such.

Hopefully this will be fixed in 2004.2? In 2004.1, the user starts out 
with a completely blank make.conf, and a new one never gets copied over.


-- 
Joel Konkle-Parker
Webmaster  [Ballsome.com]

E-mail     [jjk3@msstate.edu]


--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-07-23 11:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21  8:22 [gentoo-portage-dev] a suggestion about einfo messages YiDa Chiang
2004-07-21  9:04 ` Michael Kohl
2004-07-21 15:29   ` Joseph Booker
2004-07-21 15:51     ` Michael Kohl
2004-07-21 16:15       ` Thomas de Grenier de Latour
2004-07-21 16:19         ` Michael Kohl
2004-07-21 16:01     ` Thomas de Grenier de Latour
2004-07-21 16:06       ` Joseph Booker
2004-07-21 21:30   ` [gentoo-portage-dev] " Joel Konkle-Parker
2004-07-22 20:48     ` Joseph Booker
2004-07-22 21:31       ` Joel Konkle-Parker
2004-07-23  9:08         ` Kumba
2004-07-23 11:32           ` Joel Konkle-Parker [this message]
2004-07-25 15:57           ` [gentoo-portage-dev] SSE2 and MMX2 use flags Roman Gaufman
2004-07-25 16:16             ` Marius Mauch
2004-07-25 18:06               ` Roman Gaufman

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='cdqsvl$r5q$1@sea.gmane.org' \
    --to=jjk3@msstate.edu \
    --cc=gentoo-portage-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