From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LZWXO-0001DK-G8 for garchives@archives.gentoo.org; Tue, 17 Feb 2009 20:27:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9AD91E038C; Tue, 17 Feb 2009 20:27:24 +0000 (UTC) Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.243]) by pigeon.gentoo.org (Postfix) with ESMTP id 6E0E7E038C for ; Tue, 17 Feb 2009 20:27:24 +0000 (UTC) Received: by rv-out-0708.google.com with SMTP id f25so2389391rvb.46 for ; Tue, 17 Feb 2009 12:27:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=a6L0IRxlJX5tn07fIYLSfSkzsKapkuJPFYzzqvCoblA=; b=BdOww0OK0jdKti2Gdm8yeRT7qkhAT7gLKkoMz7ZVFxGsMATSKe6wKB/+SuVqGFz/VK U9NcX5NsNLiz7zp/DUcBNvnogcuBeVTXA8PoBEBPttw4TuyGb6wuYSL/mD3Q+3mthoAr 3Ba2oLiLz1mWjozvufE0vlik39gXgy0FrBAzs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=gMEKKGqAPMRU3G4jQFG3qFiFmCnJLnpCTBdPpOMmFpdujnc2GXZ7emf1QMRR/MekXp 2x872kGbYgEjuIjV+zlCraO/FRNvVxqyufleRpZru2GPJ9EBopWPkLGaynV4ZtnNw70M 0K/o6nqBuPtAbihYThpcFmeeQnP4SunbAcGR4= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Sender: jer.gentoo@gmail.com Received: by 10.141.197.14 with SMTP id z14mr3461433rvp.63.1234902444065; Tue, 17 Feb 2009 12:27:24 -0800 (PST) In-Reply-To: <20090217194942.GB3649@comet> References: <90b936c0902170955o5c300d7evc906ef02116097fc@mail.gmail.com> <20090217194942.GB3649@comet> Date: Tue, 17 Feb 2009 14:27:24 -0600 X-Google-Sender-Auth: d74fec965487922b Message-ID: <90b936c0902171227u461bec1cl6e4b078f4c75b97c@mail.gmail.com> Subject: Re: [gentoo-dev] Time to remove app-shells/bash-completion-config From: Jeremy Olexa To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 03177ddd-9969-40ea-9715-c2f67b739799 X-Archives-Hash: c5c2ee01b1c92f39905a16c8ceed2b7e On Tue, Feb 17, 2009 at 1:49 PM, Donnie Berkholz wrote: > On 11:55 Tue 17 Feb , Jeremy Olexa wrote: >> We should only be using eselect now to enable bash-completion. I think >> bash-completion-config is broken now anyway >> (https://bugs.gentoo.org/show_bug.cgi?id=253878). So, after this >> change, I will p.mask b-c-c for removal. >> >> Any concerns? The upgrade path in the future is going to be wierd as >> upstream is releasing v1.0 soon, but that is not concern for now. > > http://bugs.gentoo.org/show_bug.cgi?id=218557 > > [Comment #0] mescalinum@gentoo.org : 2008-04-20 12:26:38 0000 > ------------------------------------------------------------------------------- > if I type: > > eselect bashcomp enable [TAB] > > I get a 'Killed' string printed to terminal: > > eselect bashcomp enable Killed > > and it messes up the bash shell (i.e. history doesn't work anymore) > > [Comment #3] w.schwiedop@web.de : 2008-07-31 00:41:39 0000 > ------------------------------------------------------------------------------- > Created an attachment (id=161784) > Replacement for the current eselect completion script This is not a fault of bash-completion but rather the eselect bash-completion module itself. Since our eselect team is defunct, I will mask the bash-completion USE flag for app-admin/eselect unless someone steps up to take care of it (working patches exist, anyone?). Analogy: If subversion's bash-completion module was broken, it wouldn't block anything to do with app-shells/bash-completion. Instead you would work it out with upstream. Also: *enabling* bash-completion modules via eselect works just fine. So, I don't get why this reply was needed on this thread. -Jeremy