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 4DC13138CCC for ; Wed, 6 May 2015 15:08:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 33D69E084A; Wed, 6 May 2015 15:08:15 +0000 (UTC) Received: from mail-qg0-f45.google.com (mail-qg0-f45.google.com [209.85.192.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 32391E0814 for ; Wed, 6 May 2015 15:08:14 +0000 (UTC) Received: by qgeb100 with SMTP id b100so5958934qge.3 for ; Wed, 06 May 2015 08:08:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZdCDqm+l7IRRX3W0BD7zer2+aTGhSpHgui5CWUj+UyY=; b=rv5MXG2/agAYeazAJIRMgjwD1m2E6f7CowmffiGHK5hdP8Ilp2D31GYZhc8guhcRCd 5vNt4uLpMdBIYzCYYqN6hXZFuVAyfuY+NegwW/Emfg1kG54jhM06eN4SARIB4Teapub1 1A2s16eKpesAuft7b+pAB4cbwbLH35b+GSHMipzK3P5SboSrFSk/A2FddXLfP7Ga/HHx dRqvAPoGM5BTrYfILH8KhfNvAHVuglHL2WwFJu/rQSMf1/wu7t+YE8Q6YzXXAWfk+Yti 55tQLhcFKZ8SgKolzwkSfJpc66lhTdtYYwXWQtXxMxf/A0Sww52VkDUJ3/HO0FipIGeD iXhw== X-Received: by 10.55.20.141 with SMTP id 13mr69113332qku.30.1430924893480; Wed, 06 May 2015 08:08:13 -0700 (PDT) Received: from [192.168.2.5] (adsl-98-95-106-170.jan.bellsouth.net. [98.95.106.170]) by mx.google.com with ESMTPSA id 69sm1303170qkr.41.2015.05.06.08.08.12 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 May 2015 08:08:12 -0700 (PDT) Message-ID: <554A2E5B.8060003@gmail.com> Date: Wed, 06 May 2015 10:08:11 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge bash-completion References: <1742401.rrymqTMobZ@bzpc> <2143716.2uHe5HlNr5@bzpc> <5549E0F3.4000602@gmail.com> <3747470.cYVnFvdpCL@bzpc> In-Reply-To: <3747470.cYVnFvdpCL@bzpc> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: a0b0ccf9-0d92-4ce3-97bb-0f7f96698bd9 X-Archives-Hash: 9af73616917b563e4e2e12532f40b6ec Behrouz Khosravi wrote: > On Wednesday, May 06, 2015 04:37:55 AM Dale wrote: > >>> This is my output: >> The P means it is in the portage tree. The I means that it is >> installed. Based on your info, you are using a older version of >> bash-completion than I am. >> >> Dale >> >> :-) :-) > Thanks, Are you on ~AMD64 ? > My version is the last in stable. > I added keyword, but It will install newer version of bash too. Is it stable ? > > I'm using this version of bash, which I'm sure is the keyworded version. app-shells/bash-4.3_p33-r2 I don't know of any issues so I guess it is OK but your system may be different too. This was mentioned in another reply but I'm putting the info here for you. This is the news item for this which could be the problem. root@fireball / # eselect news read 19 2014-11-25-bash-completion-2_1-r90 Title bash-completion-2.1-r90 Author Michał Górny Posted 2014-11-25 Revision 1 Starting with app-shells/bash-completion-2.1-r90, the framework used to enable and manage completions in Gentoo is finally changing in order to properly follow upstream design. This has some important implications for our users. Firstly, the install location for completions changes to follow upstream default. The completions enabled before the upgrade will continue to work but you may no longer be able to enable or disable completions installed prior to the upgrade. To solve this issue, the packages installing completions need to rebuilt. The following command can be used to automatically rebuild all the relevant packages: $ find /usr/share/bash-completion -maxdepth 1 -type f \ '!' -name 'bash_completion' -exec emerge -1v {} + Secondly, the autoloading support introduced upstream removes the penalties involved with enabling a great number of completions. This allowed us to switch to an opt-out model where all completions installed after the upgrade are enabled by default. Specific completions can be disabled using 'eselect bashcomp disable ...' The model change implies that all current selections done using 'eselect bashcomp' can not be properly migrated and will be disregarded when the relevant completion files are built against the new bash-completion version. After rebuilding all the packages providing completion files, you may want to remove the symlinks that were used to configure the previous framework using the following command: $ find /etc/bash_completion.d -type l -delete Thirdly, we have solved the issue causing bash-completion support to be enabled by default on login shells only. If you needed to explicitly source 'bash_completion' script in bashrc, you can safely remove that code now since system-wide bashrc takes care of loading it. Lastly, we would like to explain that USE=bash-completion is being removed from packages for the completions will be installed unconditionally now. However, this will result in some implicit dependencies being removed. Most specifically, users wishing to use bash-completion will have to request app-shells/bash-completion explicitly, e.g.: $ emerge -n app-shells/bash-completion root@fireball / # Maybe that will fix it and you can stay stable. Maybe. ;-) Dale :-) :-)