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 AB6E3138CCE for ; Thu, 7 May 2015 06:47:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B8534E08FA; Thu, 7 May 2015 06:47:39 +0000 (UTC) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (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 851A0E08E1 for ; Thu, 7 May 2015 06:47:38 +0000 (UTC) Received: by wgic8 with SMTP id c8so6900803wgi.1 for ; Wed, 06 May 2015 23:47:37 -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=T34fYVv6VwI0vJlXa6BJk9mZBU0tXACjmVMs7H9ynjk=; b=iP8Fn2IXdHeYF8UA+fBC32Rc/14qX/YvY+mCxdjT1X+tpgFgwaQcUY149nU1Mnlq/N xj45+4S1SvoegBqzOc61/2k3BDY5hHMTqJeedXi+YLZCeewm+0E7HOm/XutaIotSlRcS yeeCzbHpETNFGTCihByOeFxKhLS/XVYQLpxDWymyseYthsiBKpO3fqlawqPOk5+ScgT4 HsNfdJ55BFHOF6ujeFq2jtmRlrqhkT1INB+BsZkepQIEve2UsZuKq25d23h97ulZINSk f/jnHVeR3WfgsTRMJ67JEha9+OntN9G6iTTbSxCiyWuDXhexspywlPrtHPdKFRpERx0e pSwA== X-Received: by 10.180.206.229 with SMTP id lr5mr3823844wic.86.1430981256995; Wed, 06 May 2015 23:47:36 -0700 (PDT) Received: from [172.20.0.41] (105-237-217-30.access.mtnbusiness.co.za. [105.237.217.30]) by mx.google.com with ESMTPSA id l3sm2299507wik.16.2015.05.06.23.47.35 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 May 2015 23:47:36 -0700 (PDT) Message-ID: <554B0A86.1010803@gmail.com> Date: Thu, 07 May 2015 08:47:34 +0200 From: Alan McKinnon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 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] Re: emerge bash-completion References: <1742401.rrymqTMobZ@bzpc> <3661244.aZV5KDpgjA@bzpc> <20150506160127.2d237f99@sepulchrave.remarqs> In-Reply-To: <20150506160127.2d237f99@sepulchrave.remarqs> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 42a96bff-c38e-4493-82f0-de51d87ed808 X-Archives-Hash: b54bb47b9883b1f8c1f01ebc506b6fe4 On 06/05/2015 23:01, »Q« wrote: > On Wed, 06 May 2015 12:44:16 +0300 > Nikos Chantziaras wrote: > >> If that is the case, then in order to completely transition to the >> new system, you would have to re-emerge everything that installs >> bashcomp files. Also, delete all your bashcomp eselect files. The new >> system has everything enabled by default and eselect is used to >> actually disable bashcomp for all packages and whitelist the only you >> enable. This can cause problems if you have old and new files lying >> around. > > Thanks for this. I'm not the OP, but broken bash completion has > been bothering me for a while. Somehow I'd gotten the mistaken > impression that it was supposed to heal itself over time as the > programs that install bashcomp files were rebuilt with updates, without > me having deal with any cruft. > >> I think there was a news item on how to transition from the old to >> the new setup. No idea where to find it if you don't have it in >> "eselect news list" anymore :-/ > > At the time, I was on the lookout for such a news item and I never saw > one. Always possible that was my fault, but I really think there was > no such item. > > Also, if I've correctly understood what you wrote above, > needs an overhaul. > (Conversely, if it doesn't need an overhaul, my understanding is still > faulty and I'll be back for some hand-holding!) > > There was a news item, I've pasted the whole thing here for you 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 -- Alan McKinnon alan.mckinnon@gmail.com