Re: [gentoo-dev] bash-4.4 - call for testers

On Mon, Oct 3, 2016 at 3:09 PM, Kent Fredric wrote: > On Mon, 3 Oct 2016 14:37:15 +0800 > konsolebox wrote: > >> But anyway, what do you think about just enabling >> IUSE="+system-readline" by default to any version, and just rely on >> KEYWORDS="" to

Re: [gentoo-dev] bash-4.4 - call for testers

On Mon, 3 Oct 2016 14:37:15 +0800 konsolebox wrote: > But anyway, what do you think about just enabling > IUSE="+system-readline" by default to any version, and just rely on > KEYWORDS="" to prevent the user from misusing it with a pre-release > version of bash? I believe

Re: [gentoo-dev] bash-4.4 - call for testers

On Mon, Oct 3, 2016 at 1:53 PM, Kent Fredric wrote: > And I get the impression that the desire you have to have different > behaviour for non-rc versions is a bit niche. Not quite. I just started by siding with the current implementation which is to disable system readline in

Re: [gentoo-dev] bash-4.4 - call for testers

On Mon, 3 Oct 2016 13:32:34 +0800 konsolebox wrote: > "A useflag that entirely goes away depending on the version" (or a > flag that is implemented in one ebuild but is not on another) is > pretty common among packages and I see that as totally valid, and is > way better

Re: [gentoo-dev] bash-4.4 - call for testers

On Mon, Oct 3, 2016 at 1:37 PM, konsolebox wrote: > I created another example for this. I mistakenly renamed --with-installed-readline to --with-system-readline there, sorry. Here's the correct one. -- konsolebox bash-4.4-r1.ebuild Description: Binary data

Re: [gentoo-dev] bash-4.4 - call for testers

I examined both RC versions of bash and readline, and it turns out that the KEYWORDS are disabled in those. If that is -always- the case, we could just have IUSE='+system-readline' in any version regardless if it's a release or not, since users would not be able to install it anyway, unless they

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, Oct 2, 2016 at 7:42 PM, Kent Fredric wrote: > On Sun, 2 Oct 2016 18:18:17 +0800 > konsolebox wrote: > >> I should also add that a dynamic "default" that varies depending on >> the version doesn't sound good to me. For one at least, it confuses >>

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, 2 Oct 2016 18:18:17 +0800 konsolebox wrote: > I should also add that a dynamic "default" that varies depending on > the version doesn't sound good to me. For one at least, it confuses > the user. I agree that its a bit unintuitive. However, the alternatives are:

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, Oct 2, 2016 at 6:00 PM, konsolebox wrote: > On Sun, Oct 2, 2016 at 4:58 PM, Kent Fredric wrote: >> On Sun, 2 Oct 2016 16:03:11 +0800 >> konsolebox wrote: >> >>> I actually don't like the idea of enabling or disabling >>>

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, Oct 2, 2016 at 4:58 PM, Kent Fredric wrote: > On Sun, 2 Oct 2016 16:03:11 +0800 > konsolebox wrote: > >> I actually don't like the idea of enabling or disabling >> "installed-readline" based on the `${PV} != *_rc*` condition. If a >> user would

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, 2 Oct 2016 16:03:11 +0800 konsolebox wrote: > I actually don't like the idea of enabling or disabling > "installed-readline" based on the `${PV} != *_rc*` condition. If a > user would want to explicitly enable "installed-readline" globally, > how would he make sure

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, Oct 2, 2016 at 1:40 PM, Kent Fredric wrote: > On Sun, 2 Oct 2016 13:28:04 +0800 > konsolebox wrote: > >> I guess that's another good way to solve the readline issue (when it >> comes to bash). But I'd prefer that it's not done automatically. >>

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, 2 Oct 2016 13:28:04 +0800 konsolebox wrote: > I guess that's another good way to solve the readline issue (when it > comes to bash). But I'd prefer that it's not done automatically. > Instead we should add a formal use flag like 'installed-readline'. We > can add

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, Oct 2, 2016 at 1:28 PM, konsolebox wrote: > On Sun, Oct 2, 2016 at 12:34 AM, Dan Douglas wrote: >> I'd be perfectly happy requiring bundled readline when USE="readline" >> for bash versions incompatible with the installed readline, > > I guess

Re: [gentoo-dev] bash-4.4 - call for testers

On Sun, Oct 2, 2016 at 12:34 AM, Dan Douglas wrote: > I'd be perfectly happy requiring bundled readline when USE="readline" > for bash versions incompatible with the installed readline, I guess that's another good way to solve the readline issue (when it comes to bash). But

Re: [gentoo-dev] bash-4.4 - call for testers

On Sat, Oct 1, 2016 at 4:48 PM, Dan Douglas wrote: > One note - it may be useful to install `BASH_LOADABLES_PATH=/usr/lib/bash` > to the global env.d environment when USE=plugins, now that bash has > this feature. It doesn't enable anything by default but just informs bash that

Re: [gentoo-dev] bash-4.4 - call for testers

One note - it may be useful to install `BASH_LOADABLES_PATH=/usr/lib/bash` to the global env.d environment when USE=plugins, now that bash has this feature. It doesn't enable anything by default but just informs bash that it can look for loadables in that location. (ins)ormaaj@smorgbox ~ $

Re: [gentoo-dev] bash-4.4 - call for testers

On Sat, Oct 1, 2016 at 10:40 AM, konsolebox wrote: > I should also add that testing newer versions of bash becomes more > risky sometimes, since bash would sometimes need a newer version of > readline (see >

Re: [gentoo-dev] bash-4.4 - call for testers

I should also add that testing newer versions of bash becomes more risky sometimes, since bash would sometimes need a newer version of readline (see https://lists.gnu.org/archive/html/bug-bash/2016-09/msg00020.html). Rebuilding or installing a newer version of readline would cause some other

Re: [gentoo-dev] bash-4.4 - call for testers

On Sat, Oct 1, 2016 at 8:38 AM, Kent Fredric wrote: > On Sat, 1 Oct 2016 01:49:56 +0800 > konsolebox wrote: > >> It would be nice to have some eselect command to >> easily switch from one version of Bash to another; probably something >> close to how it's

Re: [gentoo-dev] bash-4.4 - call for testers

On Thu, Sep 29, 2016 at 5:29 PM, Kent Fredric wrote: > Maybe you could do some horrible QA Violation like USE=multislot > which changes the slot from :0 and adds the -suffix at the same time. > > But I still don't think its a useful or good idea. Really? Why is this a problem?

Re: [gentoo-dev] bash-4.4 - call for testers

> I am against it as well. The purpose of this testing is to eventually > move to bash-4.4 being stable and replacing bash-4.3, so slotting it > would make that more complex later. Only true for users that have no interest in testing. Irrelevant for anyone that needs to test for backwards

Re: [gentoo-dev] bash-4.4 - call for testers

On Sat, 1 Oct 2016 01:49:56 +0800 konsolebox wrote: > It would be nice to have some eselect command to > easily switch from one version of Bash to another; probably something > close to how it's done in dev-lang/ruby. Its just eselect itself is bash. So if bash is broken

Re: [gentoo-dev] bash-4.4 - call for testers

On Fri, Sep 30, 2016 at 5:56 AM, Andy Mender wrote: > Would it be OK to have the real stable version (now, Bash 4.3) as slot :0 > and a single testing version (now, Bash 4.4) as slot:1 in addition to > needing the "~amd64" flag? Or simply 4.3 and 4.4, not 0 and 1. And

Re: [gentoo-dev] bash-4.4 - call for testers

On Thu, Sep 29, 2016 at 1:54 PM, Dan Douglas wrote: > The only reason I haven't been testing this for many months > system-wide is it's in the same slot as 4.3, and it still is. Is it > not possible to separate them? That would also be helpful to me since I closely monitor the

Re: [gentoo-dev] bash-4.4 - call for testers

Alright then, I will give bash4.4 a try and if there are any problems, I'll file a proper bug report. Best regards, Andy On 30 September 2016 at 15:38, William Hubbs wrote: > On Fri, Sep 30, 2016 at 11:29:05AM +1300, Kent Fredric wrote: > > On Thu, 29 Sep 2016 23:56:34

Re: [gentoo-dev] bash-4.4 - call for testers

On Fri, Sep 30, 2016 at 11:29:05AM +1300, Kent Fredric wrote: > On Thu, 29 Sep 2016 23:56:34 +0200 > Andy Mender wrote: > > > I believe the main problem comes from /bin/bash and potential symlinks that > > would need to be introduced as part of the slotting. > > In a

Re: [gentoo-dev] bash-4.4 - call for testers

On Thu, 29 Sep 2016 23:56:34 +0200 Andy Mender wrote: > I believe the main problem comes from /bin/bash and potential symlinks that > would need to be introduced as part of the slotting. In a pinch you could probably get away with calling :1 /usr/bin/bash-4.4 instead

Re: [gentoo-dev] bash-4.4 - call for testers

Yes, I also wouldn't want to sacrifice something as relevant as the default Shell interpreter. I quickly checked other GNU/Linux distributions and even on Arch Linux Bash 4.3 seems to be the newest stable version. Would it be OK to have the real stable version (now, Bash 4.3) as slot :0 and a

Re: [gentoo-dev] bash-4.4 - call for testers

The only reason I haven't been testing this for many months system-wide is it's in the same slot as 4.3, and it still is. Is it not possible to separate them?

Re: [gentoo-dev] bash-4.4 - call for testers

Hello, On Thu, 22 Sep 2016, David Haller wrote: [..] >I've found this that I guess has to do with the new readline: > >>From the build.log of >emerge -1 dev-lisp/clisp > > >[..] > * Package:dev-lisp/clisp-2.49-r8 > * Repository: gentoo > * Maintainer: common-l...@gentoo.org > * USE:

Re: [gentoo-dev] bash-4.4 - call for testers

Hello, On Tue, 20 Sep 2016, Lars Wendler wrote: >This is a call for testers. If you feel brave enough, please give >bash-4.4 a shot and report all problems you might have with it. > >Add the following to you package.unmask file/directory: > > =app-shells/bash-4.4* > =sys-libs/readline-7.0*