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: News item 1: changes to stages (make.conf and make.profile)
Date: Wed, 12 Sep 2012 00:02:30 +0000 (UTC)	[thread overview]
Message-ID: <pan.2012.09.12.00.02.31@cox.net> (raw)
In-Reply-To: 504F66F0.1040305@gentoo.org

Zac Medico posted on Tue, 11 Sep 2012 09:29:36 -0700 as excerpted:

> I would recommend to simply use /etc/make.conf alone until the legacy
> tools that you use catch up. We have to change the default location in
> the stages in order to expose the bugs so they can get fixed.

I posted to the portage-dev list about this so you probably already know,
but for others, particularly users, following this transition thread:

Gentoo's bash-completion breaks when make.conf is in /etc/portage.  Bug
filed back in early July and there's a simple enough patch, but
app-shells/gentoo-bashcomp has only the shell-tools herd, no dedicated
maintainer, and 13 open bugs including this one, all apparently portage
(or gentoolkit) related, with the last release in 2010 (Dec) with
stabilization a month later.  So it's not seeing a lot of movement.

https://bugs.gentoo.org/show_bug.cgi?id=424777

So anyone who depends on tab-completion for their emerge commands, etc,
may want to either hold off on the move or apply the patch manually, until
this is fixed.

FWIW here's the listing of all open app-shells/gentoo-bashcomp bugs:

https://bugs.gentoo.org/buglist.cgi?quicksearch=app-shells%2Fgentoo-bashcomp

-- 
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



  reply	other threads:[~2012-09-12  0:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06  3:52 [gentoo-dev] News item 1: changes to stages (make.conf and make.profile) Jorge Manuel B. S. Vicetto
2012-09-06  5:30 ` Ulrich Mueller
2012-09-06  6:36   ` [gentoo-dev] " Duncan
2012-09-08 18:05 ` [gentoo-dev] " Jorge Manuel B. S. Vicetto
2012-09-08 18:56   ` [gentoo-dev] " Duncan
2012-09-09 18:56   ` [gentoo-dev] " Aaron W. Swenson
2012-09-09 20:13 ` Jorge Manuel B. S. Vicetto
2012-09-09 21:42   ` Doug Goldstein
2012-09-09 21:57     ` Zac Medico
2012-09-10  0:59       ` [gentoo-dev] " Duncan
2012-09-10  1:34         ` Zac Medico
2012-09-10  6:06           ` Duncan
2012-09-11  3:29           ` Gregory M. Turner
2012-09-11  5:39             ` Duncan
2012-09-12  9:16               ` Gregory M. Turner
2012-09-12 10:04                 ` Zac Medico
2012-09-11 16:29             ` Zac Medico
2012-09-12  0:02               ` Duncan [this message]
2012-09-12  3:55                 ` Ben de Groot
2012-09-10  1:34         ` Duncan

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.2012.09.12.00.02.31@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